[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49469e9f-ca42-4250-b949-66247f623c3d@suse.cz>
Date: Tue, 8 Oct 2024 11:17:51 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: "Christoph Lameter (Ampere)" <cl@...two.org>,
Hyeonggon Yoo <42.hyeyoo@...il.com>
Cc: "yuan.gao" <yuan.gao@...oud.cn>, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com, akpm@...ux-foundation.org, roman.gushchin@...ux.dev,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] mm/slub: Avoid list corruption when removing a slab
from the full list
On 10/7/24 18:40, Christoph Lameter (Ampere) wrote:
>
> list_del() in remove_partial() sets poison values for next/prev so there
> should no list
> corruption but a failure showing the poison values.
Yeah that's what is reported, but there's still a mention of list corruption:
[ 4277.385669] list_del corruption, ffffea00044b3e50->next is LIST_POISON1 (dead000000000100)
> static inline void list_del(struct list_head *entry)
> {
> __list_del_entry(entry);
> entry->next = LIST_POISON1;
> entry->prev = LIST_POISON2;
> }
>
Powered by blists - more mailing lists