[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <69f719ab-8251-e6c1-5c10-0f89fc6413b9@gentwo.org>
Date: Tue, 15 Oct 2024 09:38:57 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Vlastimil Babka <vbabka@...e.cz>
cc: David Rientjes <rientjes@...gle.com>, "yuan.gao" <yuan.gao@...oud.cn>,
penberg@...nel.org, iamjoonsoo.kim@....com, akpm@...ux-foundation.org,
roman.gushchin@...ux.dev, 42.hyeyoo@...il.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] mm/slub: Avoid list corruption when removing a slab
from the full list
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.
Powered by blists - more mailing lists