From: David Rientjes <rientjes@google.com>
To: "yuan.gao" <yuan.gao@ucloud.cn>
Cc: "Christoph Lameter (Ampere)" <cl@gentwo.org>,
penberg@kernel.org, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, vbabka@suse.cz,
roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm/slub: Avoid list corruption when removing a slab from the full list
Date: Sun, 13 Oct 2024 13:46:13 -0700 (PDT) [thread overview]
Message-ID: <572f7473-1781-388b-103e-d4382f58f2f9@google.com> (raw)
In-Reply-To: <i5vqm2ucpjzfbeteamphorouzoep3qxmh3prq5d76g4sazjarf@d3rfku3r5735>
On Sat, 12 Oct 2024, yuan.gao wrote:
> On 24/10/11 11:07AM, Christoph Lameter (Ampere) wrote:
> > On Fri, 11 Oct 2024, yuan.gao wrote:
> >
> > > When an object belonging to the slab got freed later, the remove_full()
> > > function is called. Because the slab is neither on the partial list nor
> > > on the full list, it eventually lead to a list corruption.
> >
> > We detect list poison....
> >
> > > diff --git a/mm/slab.h b/mm/slab.h
> > > index 6c6fe6d630ce..7681e71d9a13 100644
> > > --- a/mm/slab.h
> > > +++ b/mm/slab.h
> > > @@ -73,6 +73,10 @@ struct slab {
> > > struct {
> > > unsigned inuse:16;
> > > unsigned objects:15;
> > > + /*
> > > + * Reuse frozen bit for slab with debug enabled:
> >
> > "If slab debugging is enabled then the frozen bit can bereused to
> > indicate that the slab was corrupted"
> >
> > > index 5b832512044e..b9265e9f11aa 100644
> > > --- a/mm/slub.c
> > > +++ b/mm/slub.c
> > > @@ -1423,6 +1423,11 @@ static int check_slab(struct kmem_cache *s, struct slab *slab)
> > > slab->inuse, slab->objects);
> > > return 0;
> > > }
> > > + if (slab->frozen) {
> > > + slab_err(s, slab, "Corrupted slab");
> >
> >
> > "Slab folio disabled due to metadata corruption" ?
> >
> >
>
> Yes, that's what I meant.
> Perhaps I should change the description from "Corrupted slab" to
> "Metadata corrupt"?
>
I think the point here is that slab page corruption is different from slab
metadata corruption :)
The suggested phrasing, "Slab folio disabled due to metadata corruption",
sounds good to me.
> > > @@ -2744,7 +2750,10 @@ static void *alloc_single_from_partial(struct kmem_cache *s,
> > > slab->inuse++;
> > >
> > > if (!alloc_debug_processing(s, slab, object, orig_size)) {
> > > - remove_partial(n, slab);
> > > + if (folio_test_slab(slab_folio(slab))) {
> >
> >
> > Does folio_test_slab test for the frozen bit??
> >
>
> For slab folios, slab->fronzen has been set to 1.
> For non-slab folios, we should not call remove_partial().
> I'm not sure if I understand this correctly.
>
> Thanks
>
next prev parent reply other threads:[~2024-10-13 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 10:20 yuan.gao
2024-10-11 18:07 ` Christoph Lameter (Ampere)
2024-10-12 4:04 ` yuan.gao
2024-10-13 20:46 ` David Rientjes [this message]
2024-10-14 14:55 ` Vlastimil Babka
2024-10-14 16:47 ` Christoph Lameter (Ampere)
2024-10-15 8:56 ` Vlastimil Babka
2024-10-15 16:38 ` Christoph Lameter (Ampere)
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=572f7473-1781-388b-103e-d4382f58f2f9@google.com \
--to=rientjes@google.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=yuan.gao@ucloud.cn \
/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