From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Michal Hocko <mhocko@kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
Qian Cai <cai@lca.pw>, Jan Kara <jack@suse.cz>,
kirill.shutemov@linux.intel.com, songliubraving@fb.com,
william.kucharski@oracle.com
Subject: Re: kernel BUG at mm/swap_state.c:170!
Date: Fri, 5 Jul 2019 20:19:48 +0500 [thread overview]
Message-ID: <CABXGCsOizgLhJYUDos+ZVPZ5iV3gDeAcSpgvg-weVchgOsTjcA@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsOpj_E7jL9OpMX4wZbMktiF=9WOyeTv1R-W59gFMGC7mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hey folks.
Excuse me, is anybody read my previous message?
5.2-rc7 is still affected by this issue [the logs in file
dmesg-5.2rc7-0.1.tar.xz] and I worry that stable 5.2 would be released
with this bug because there is almost no time left and I didn't see
the attention to this problem.
I confirm that reverting commit 5fd4ca2d84b2 on top of the rc7 tag is
help fix it [the logs in file dmesg-5.2rc7-0.2.tar.xz].
I am still awaiting any feedback here.
Thanks.
--
Best Regards,
Mike Gavrilov.
[-- Attachment #2: dmesg-5.2rc7-0.1.tar.xz --]
[-- Type: application/octet-stream, Size: 180512 bytes --]
[-- Attachment #3: dmesg-5.2rc7-0.2.tar.xz --]
[-- Type: application/octet-stream, Size: 14444 bytes --]
next prev parent reply other threads:[~2019-07-05 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 4:05 Mikhail Gavrilov
2019-05-29 17:32 ` Mikhail Gavrilov
2019-05-29 18:09 ` Michal Hocko
2019-05-29 19:28 ` Mikhail Gavrilov
2019-06-05 20:07 ` Mikhail Gavrilov
2019-06-11 3:59 ` Mikhail Gavrilov
2019-06-16 10:12 ` Mikhail Gavrilov
2019-06-17 12:17 ` Vlastimil Babka
2019-06-17 20:09 ` Mikhail Gavrilov
2019-06-30 21:15 ` Mikhail Gavrilov
2019-07-05 15:19 ` Mikhail Gavrilov [this message]
2019-07-05 23:03 ` Jan Kara
2019-07-06 2:39 ` Linus Torvalds
2019-06-17 12:47 ` Vlastimil Babka
2019-07-22 1:37 ` huang ying
2019-07-22 7:31 ` Mikhail Gavrilov
2019-07-22 7:52 ` Huang, Ying
2019-07-22 7:56 ` Mikhail Gavrilov
2019-07-23 5:08 ` Huang, Ying
2019-07-25 6:17 ` Mikhail Gavrilov
2019-07-25 7:14 ` Huang, Ying
2019-07-25 11:44 ` Matthew Wilcox
2019-07-26 3:20 ` Huang, Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABXGCsOizgLhJYUDos+ZVPZ5iV3gDeAcSpgvg-weVchgOsTjcA@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=cai@lca.pw \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=songliubraving@fb.com \
--cc=vbabka@suse.cz \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox