From: Suren Baghdasaryan <surenb@google.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Hao Ge <hao.ge@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry.yoo@oracle.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hao Ge <gehao@kylinos.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] slab: Avoid race on slab->obj_exts in alloc_slab_obj_exts
Date: Tue, 21 Oct 2025 06:24:53 -0700 [thread overview]
Message-ID: <CAJuCfpFto6=Z0kPdjNP6WeOYUB0uMKom9+HFg+ugA=ZjsNhewA@mail.gmail.com> (raw)
In-Reply-To: <1e1376fd-1d38-4dde-918a-d4e937d4feac@suse.cz>
On Tue, Oct 21, 2025 at 12:04 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>
> On 10/21/25 03:03, Hao Ge wrote:
> > From: Hao Ge <gehao@kylinos.cn>
> >
> > If two competing threads enter alloc_slab_obj_exts() and one of them
> > fails to allocate the object extension vector, it might override the
> > valid slab->obj_exts allocated by the other thread with
> > OBJEXTS_ALLOC_FAIL. This will cause the thread that lost this race and
> > expects a valid pointer to dereference a NULL pointer later on.
> >
> > Update slab->obj_exts atomically using cmpxchg() to avoid
> > slab->obj_exts overrides by racing threads.
> >
> > Thanks for Vlastimil and Suren's help with debugging.
> >
> > Fixes: f7381b911640 ("slab: mark slab->obj_exts allocation failures unconditionally")
> > Cc: <stable@vger.kernel.org>
> > Suggested-by: Suren Baghdasaryan <surenb@google.com>
> > Signed-off-by: Hao Ge <gehao@kylinos.cn>
Reviewed-by: Suren Baghdasaryan <surenb@google.com>
Thanks for the fix, Hao!
>
> Added to slab/for-next-fixes, thanks!
>
> > ---
> > v3: According to Suren's suggestion, simplify the commit message and the code comments.
> > Thanks for Suren.
> >
> > v2: Incorporate handling for the scenario where, if mark_failed_objexts_alloc wins the race,
> > the other process (that previously succeeded in allocation) will lose the race, based on Suren's suggestion.
> > Add Suggested-by: Suren Baghdasaryan <surenb@google.com>
> > ---
> > mm/slub.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/mm/slub.c b/mm/slub.c
> > index 2e4340c75be2..d4403341c9df 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
> > @@ -2054,7 +2054,7 @@ static inline void mark_objexts_empty(struct slabobj_ext *obj_exts)
> >
> > static inline void mark_failed_objexts_alloc(struct slab *slab)
> > {
> > - slab->obj_exts = OBJEXTS_ALLOC_FAIL;
> > + cmpxchg(&slab->obj_exts, 0, OBJEXTS_ALLOC_FAIL);
> > }
> >
> > static inline void handle_failed_objexts_alloc(unsigned long obj_exts,
> > @@ -2136,6 +2136,7 @@ int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
> > #ifdef CONFIG_MEMCG
> > new_exts |= MEMCG_DATA_OBJEXTS;
> > #endif
> > +retry:
> > old_exts = READ_ONCE(slab->obj_exts);
> > handle_failed_objexts_alloc(old_exts, vec, objects);
> > if (new_slab) {
> > @@ -2145,8 +2146,7 @@ int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
> > * be simply assigned.
> > */
> > slab->obj_exts = new_exts;
> > - } else if ((old_exts & ~OBJEXTS_FLAGS_MASK) ||
> > - cmpxchg(&slab->obj_exts, old_exts, new_exts) != old_exts) {
> > + } else if (old_exts & ~OBJEXTS_FLAGS_MASK) {
> > /*
> > * If the slab is already in use, somebody can allocate and
> > * assign slabobj_exts in parallel. In this case the existing
> > @@ -2158,6 +2158,9 @@ int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
> > else
> > kfree(vec);
> > return 0;
> > + } else if (cmpxchg(&slab->obj_exts, old_exts, new_exts) != old_exts) {
> > + /* Retry if a racing thread changed slab->obj_exts from under us. */
> > + goto retry;
> > }
> >
> > if (allow_spin)
>
prev parent reply other threads:[~2025-10-21 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 1:03 Hao Ge
2025-10-21 2:16 ` Harry Yoo
2025-10-21 7:04 ` Vlastimil Babka
2025-10-21 13:24 ` Suren Baghdasaryan [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='CAJuCfpFto6=Z0kPdjNP6WeOYUB0uMKom9+HFg+ugA=ZjsNhewA@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=gehao@kylinos.cn \
--cc=hao.ge@linux.dev \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--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