From: "Gregory Price (Meta)" <gourry@gourry.net>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: shao.mingyin@zte.com.cn, akpm@linux-foundation.org,
david@kernel.org, linux-mm@kvack.org, ziy@nvidia.com,
matthew.brost@intel.com, joshua.hahnjy@gmail.com,
byungchul@sk.com, gourry@gourry.net,
ying.huang@linux.alibaba.com, apopple@nvidia.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/migrate: fix softlockup in do_pages_move() with huge page arrays
Date: Sat, 14 Nov 2026 15:33:45 -0500 [thread overview]
Message-ID: <179468842502.482102.17860580592179578567.b4-reply@b4> (raw)
In-Reply-To: <avifKRgR0Q4WPUNR@gremlin>
On 2026-11-14 17:51 +0000, Lorenzo Stoakes (ARM) wrote:
> On Sun, Nov 08, 2026 at 02:28:31PM +0800, shao.mingyin@zte.com.cn wrote:
> > From: Shao Mingyin <shao.mingyin@zte.com.cn>
> >
> > do_pages_stat() had the same problem; it was fixed by 8e934ab44389. In
> > current mainline only alpha, hexagon and classic m68k can select
> > PREEMPT_NONE and they cannot enable CONFIG_NUMA, so this mainly targets
> > pre-v7.0 stable kernels.
> >
> > Fixes: a49bd4d71637 ("mm, numa: rework do_pages_move")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>
>
> NAK.
...
> And absolutely not to this person/script doing backports, thanks.
Have to agree here. This is just creating backport busywork.
This might matter if we intended to do automated cross-arch testing
on QEMU TCG on these platforms... on those LTS kernels... but also
mehhhhhh
Yeah we shouldn't encourage this kind of patch spew.
--
~Gregory
next prev parent reply other threads:[~2026-11-14 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 6:28 shao.mingyin
2026-11-09 12:19 ` David Hildenbrand (Arm)
2026-11-09 12:33 ` shao.mingyin
2026-11-09 12:45 ` David Hildenbrand (Arm)
2026-11-09 12:56 ` David Hildenbrand
2026-11-10 2:53 ` Zi Yan
2026-11-14 17:51 ` Lorenzo Stoakes (ARM)
2026-11-14 20:33 ` Gregory Price (Meta) [this message]
2026-11-15 17:02 ` David Hildenbrand (Arm)
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=179468842502.482102.17860580592179578567.b4-reply@b4 \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=matthew.brost@intel.com \
--cc=shao.mingyin@zte.com.cn \
--cc=stable@vger.kernel.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/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
all inboxes | Powered by JetHome®