From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Qian Cai <cai@lca.pw>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
linux-mm <linux-mm@kvack.org>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: kernel BUG at include/linux/mm.h:1020!
Date: Tue, 19 Mar 2019 19:13:24 -0400 [thread overview]
Message-ID: <CA+CK2bA6J_BT9C=-ohezTj4L9TV61GCi9MsKbhGO4ZtEBvdkeA@mail.gmail.com> (raw)
In-Reply-To: <1553024101.26196.8.camel@lca.pw>
Thank you Qian, do you happen to have qemu arguments that you used?
Thank you,
Pasha
On Tue, Mar 19, 2019 at 3:35 PM Qian Cai <cai@lca.pw> wrote:
>
> On Tue, 2019-03-19 at 15:27 -0400, Pavel Tatashin wrote:
> > > So reverting this patch on the top of the mainline fixed the memory
> > > corruption
> > > for me or at least make it way much harder to reproduce.
> > >
> > > dbe2d4e4f12e ("mm, compaction: round-robin the order while searching the
> > > free
> > > lists for a target")
> > >
> > > This is easy to reproduce on both KVM and bare-metal using the reproducer.
> > >
> > > # swapoff -a
> > > # i=0; while :; do i=$((i+1)); echo $i | tee /tmp/log ;
> > > /opt/ltp/testcases/bin/oom01; sleep 5; done
> > >
> > > The memory corruption always happen within 300 tries. With the above patch
> > > reverted, both the mainline and linux-next survives with 1k+ attempts so
> > > far.
> >
> > Could you please share copy of your config.
>
> https://git.sr.ht/~cai/linux-debug/tree/master/config
next prev parent reply other threads:[~2019-03-19 23:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:55 kernel BUG at include/linux/mm.h:1020! Mikhail Gavrilov
2019-03-15 20:58 ` Daniel Jordan
2019-03-15 21:34 ` Qian Cai
2019-03-17 15:22 ` Mel Gorman
2019-03-19 19:14 ` Qian Cai
2019-03-19 19:27 ` Pavel Tatashin
2019-03-19 19:35 ` Qian Cai
2019-03-19 23:13 ` Pavel Tatashin [this message]
2019-03-19 23:26 ` Qian Cai
2019-03-20 14:20 ` Mel Gorman
2019-03-20 21:50 ` Mikhail Gavrilov
2019-03-21 5:39 ` Mikhail Gavrilov
2019-03-21 13:21 ` Qian Cai
2019-03-21 15:08 ` Mikhail Gavrilov
2019-03-21 15:48 ` Qian Cai
2019-03-21 18:57 ` Mikhail Gavrilov
2019-03-21 19:14 ` Qian Cai
2019-03-22 3:41 ` Mikhail Gavrilov
2019-03-22 13:43 ` Qian Cai
2019-03-22 11:15 ` Mel Gorman
2019-03-23 4:40 ` Mikhail Gavrilov
2019-03-25 10:58 ` Mel Gorman
2019-03-25 16:06 ` Mikhail Gavrilov
2019-03-25 20:31 ` Mel Gorman
2019-03-26 4:03 ` Mikhail Gavrilov
2019-03-26 12:03 ` Mel Gorman
2019-03-27 3:57 ` Mikhail Gavrilov
2019-03-27 8:54 ` Mel Gorman
2019-03-22 7:39 ` Oscar Salvador
2019-03-22 7:54 ` Mikhail Gavrilov
2019-03-22 8:55 ` Oscar Salvador
2019-03-22 8:56 ` Oscar Salvador
2019-03-22 17:49 ` Mikhail Gavrilov
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='CA+CK2bA6J_BT9C=-ohezTj4L9TV61GCi9MsKbhGO4ZtEBvdkeA@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=cai@lca.pw \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.