All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
	gabriele balducci <balducci@units.it>
Subject: Re: [Bug 203715] New: BUG: unable to handle kernel NULL pointer dereference under stress (possibly related to https://lkml.org/lkml/2019/5/24/292 ?)
Date: Tue, 4 Jun 2019 12:05:10 +0100	[thread overview]
Message-ID: <20190604110510.GA4626@techsingularity.net> (raw)
In-Reply-To: <20190529160423.57c5a79115f350c3ebf025f9@linux-foundation.org>

On Wed, May 29, 2019 at 04:04:23PM -0700, Andrew Morton wrote:
> 
> 
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> 
> Mel, we may have a regression from e332f741a8dd1 ("mm, compaction: be
> selective about what pageblocks to clear skip hints").  The crash sure
> looks like the one which 60fce36afa9c77c7 ("mm/compaction.c: correct
> zone boundary handling when isolating pages from a pageblock") fixed,
> but Gabriele can reproduce it with 5.1.5.  I've confirmed that 5.1.5
> has 60fce36afa9c77c7.
> 

Sorry, I was on holidays and only playing catchup now. Does this happen
to trigger with 5.2-rc3? I ask because there were other fixes in there
with stable cc'd that have not been picked up yet. They are a poor match
for this particular bug but it would be nice to confirm.

-- 
Mel Gorman
SUSE Labs


  reply	other threads:[~2019-06-04 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-203715-27@https.bugzilla.kernel.org/>
2019-05-29 23:04 ` [Bug 203715] New: BUG: unable to handle kernel NULL pointer dereference under stress (possibly related to https://lkml.org/lkml/2019/5/24/292 ?) Andrew Morton
2019-06-04 11:05   ` Mel Gorman [this message]
2019-06-04 11:43     ` balducci
2019-06-05 12:38     ` balducci
2019-06-05 12:48       ` Mel Gorman
2019-06-05 17:21       ` Mel Gorman
2019-06-06 13:20         ` balducci
2019-06-06 14:44           ` Mel Gorman
2019-06-11  9:03             ` Mel Gorman
2019-06-11  9:30               ` balducci

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=20190604110510.GA4626@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=balducci@units.it \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.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 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.