From: Mel Gorman <mgorman@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org,
Michael Holzheu <holzheu@linux.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [-next 20190118] "kernel BUG at mm/page_alloc.c:3112!"
Date: Fri, 25 Jan 2019 08:44:36 +0000 [thread overview]
Message-ID: <20190125084436.GA26418@suse.de> (raw)
In-Reply-To: <20190125080307.GA3561@osiris>
On Fri, Jan 25, 2019 at 09:03:07AM +0100, Heiko Carstens wrote:
> On Mon, Jan 21, 2019 at 04:37:47PM +0000, Mel Gorman wrote:
> > On Mon, Jan 21, 2019 at 05:06:07PM +0100, Michal Hocko wrote:
> > > This sounds familiar. Cc Mel and Vlastimil.
> > >
> >
> > There is a series sitting in Andrew's inbox that replaces a compaction
> > series. A patch is dropped in the new version that deals with pages
> > getting freed during compaction that *may* be allowing active pages to
> > reach the free list and not tripping a warning like it should. I'm hoping
> > it'll be picked up soon to see if this particular bug persists or if it's
> > something else.
>
> Has this been picked up already? With linux next 20190124 I still get this:
>
Unfortunately not. Andrew will hopefully be online next week to pick it
up.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2019-01-25 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 15:43 [-next 20190118] "kernel BUG at mm/page_alloc.c:3112!" Heiko Carstens
2019-01-21 16:06 ` Michal Hocko
2019-01-21 16:37 ` Mel Gorman
2019-01-25 8:03 ` Heiko Carstens
2019-01-25 8:44 ` Mel Gorman [this message]
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=20190125084436.GA26418@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).