linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
	"yuan.gao" <yuan.gao@ucloud.cn>,
	 penberg@kernel.org, iamjoonsoo.kim@lge.com,
	akpm@linux-foundation.org,  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: Tue, 15 Oct 2024 09:38:57 -0700 (PDT)	[thread overview]
Message-ID: <69f719ab-8251-e6c1-5c10-0f89fc6413b9@gentwo.org> (raw)
In-Reply-To: <81fc4d8e-fb9f-4e7e-bbb9-dd3f53123398@suse.cz>

On Tue, 15 Oct 2024, Vlastimil Babka wrote:

> On 10/14/24 18:47, Christoph Lameter (Ampere) wrote:
> > On Mon, 14 Oct 2024, Vlastimil Babka wrote:
> >
> >> What about:
> >>
> >> "Slab disabled due to previous consistency check failure" ?
> >
> > I think this implies more than we can actually check. We can only check
> > the metadata generated by SLUB. The consistency check for the object
> > itself does not exist and would have to be done by the subsystem.
>
> "Slab disabled since SLUB metadata consistency check failure" ?

   "failed"

Sounds good.



      reply	other threads:[~2024-10-15 16:50 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
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) [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=69f719ab-8251-e6c1-5c10-0f89fc6413b9@gentwo.org \
    --to=cl@gentwo.org \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --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