From: Gregory Price <gourry@gourry.net>
To: linux-mm@kvack.org, cgroups@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
longman@redhat.com, ridong.chen@linux.dev, tj@kernel.org,
hannes@cmpxchg.org, mkoutny@suse.com, akpm@linux-foundation.org,
vbabka@kernel.org, surenb@google.com, mhocko@suse.com,
brendan.jackman@linux.dev, ziy@nvidia.com, david@kernel.org,
mgorman@techsingularity.net
Subject: Re: [PATCH 0/2] mm: fix two allocator races with zonelist and cpuset updates
Date: Fri, 16 Oct 2026 12:44:31 -0400 [thread overview]
Message-ID: <atJUCRRcgRkTPigw@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20261014222456.2318284-1-gourry@gourry.net>
On Wed, Oct 14, 2026 at 06:24:54PM -0400, Gregory Price (Meta) wrote:
> Two small fixes for lockless allocator checks that can act on an
> inconsistent view of state another CPU is updating.
>
> Neither of these are stable-worthy.
>
I'm going to need to repackage this with some additional race fixes:
https://lore.kernel.org/linux-mm/20261015210539.3243563-1-gourry@gourry.net/
+ 2 others not posted yet.
There's some mild conflicts with the CONFIG bits that make the entire
series worth backporting for ease.
~Gregory
prev parent reply other threads:[~2026-10-16 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 22:24 Gregory Price (Meta)
2026-10-14 22:24 ` [PATCH 1/2] mm/page_alloc: detect zonelist rebuilds from memory hot-add Gregory Price (Meta)
2026-10-15 7:51 ` Vlastimil Babka (SUSE)
2026-10-14 22:24 ` [PATCH 2/2] cgroup/cpuset: use mems_allowed_seq when checking a policy nodemask Gregory Price (Meta)
2026-10-15 7:59 ` Vlastimil Babka (SUSE)
2026-10-15 13:38 ` Gregory Price
2026-10-15 13:49 ` Vlastimil Babka (SUSE)
2026-10-16 16:44 ` Gregory Price [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=atJUCRRcgRkTPigw@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=cgroups@vger.kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=vbabka@kernel.org \
--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®