From: "Akira Naribayashi (Fujitsu)" <a.naribayashi@fujitsu.com>
To: 'Mel Gorman' <mgorman@techsingularity.net>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"rientjes@google.com" <rientjes@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Akira Naribayashi (Fujitsu)" <a.naribayashi@fujitsu.com>
Subject: RE: [PATCH] mm, compaction: fix fast_isolate_around() to stay within boundaries
Date: Wed, 9 Nov 2022 05:41:12 +0000 [thread overview]
Message-ID: <TYCPR01MB7775D957483C895456CFE146E53E9@TYCPR01MB7775.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20221107154350.34brdl3ms2ve5wud@techsingularity.net>
On Mon, 7 Nov 2022 15:43:56 +0000, Mei Gorman wrote:
> On Mon, Nov 07, 2022 at 12:32:34PM +0000, Akira Naribayashi (Fujitsu) wrote:
> > > Under what circumstances will this panic occur? I assume those
> > > circumstnces are pretty rare, give that 6e2b7044c1992 was nearly two
> > > years ago.
> > >
> > > Did you consider the desirability of backporting this fix into earlier
> > > kernels?
> >
> >
> > Panic can occur on systems with multiple zones in a single pageblock.
> >
>
> Please provide an example of the panic and the zoneinfo.
This issue is occurring in our customer's environment and cannot
be shared publicly as it contains customer information.
Also, the panic is occurring with the kernel in RHEL and may not
panic with Upstream's community kernel.
In other words, it is possible to panic on older kernels.
I think this fix should be backported to stable kernel series.
> > The reason it is rare is that it only happens in special configurations.
>
> How is this special configuration created?
This is the case when the node boundary is not aligned to pageblock boundary.
next prev parent reply other threads:[~2022-11-09 5:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221026112438.236336-1-a.naribayashi@fujitsu.com>
2022-10-27 20:25 ` Andrew Morton
2022-11-04 11:45 ` Mel Gorman
[not found] ` <20221031073559.36021-1-a.naribayashi@fujitsu.com>
2022-11-07 12:32 ` Akira Naribayashi (Fujitsu)
2022-11-07 15:43 ` Mel Gorman
2022-11-09 5:41 ` Akira Naribayashi (Fujitsu) [this message]
2022-11-23 10:25 ` Mel Gorman
2022-12-09 9:19 ` Akira Naribayashi (Fujitsu)
2022-12-16 10:24 ` Mel Gorman
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=TYCPR01MB7775D957483C895456CFE146E53E9@TYCPR01MB7775.jpnprd01.prod.outlook.com \
--to=a.naribayashi@fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=rientjes@google.com \
--cc=stable@vger.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