linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: "yuan.gao" <yuan.gao@ucloud.cn>,
	penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
	akpm@linux-foundation.org, roman.gushchin@linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/slub: Avoid list corruption when removing a slab from the full list
Date: Tue, 8 Oct 2024 11:17:51 +0200	[thread overview]
Message-ID: <49469e9f-ca42-4250-b949-66247f623c3d@suse.cz> (raw)
In-Reply-To: <006695cb-368c-9afc-80b5-29338e85ab99@gentwo.org>

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;
> }
> 



  reply	other threads:[~2024-10-08  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07  9:18 yuan.gao
2024-10-07 14:29 ` Vlastimil Babka
2024-10-07 15:03   ` Hyeonggon Yoo
2024-10-07 16:00     ` Christoph Lameter (Ampere)
2024-10-07 16:40       ` Christoph Lameter (Ampere)
2024-10-08  9:17         ` Vlastimil Babka [this message]
2024-10-08 13:28           ` yuan.gao
2024-10-08 10:25     ` Vlastimil Babka

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=49469e9f-ca42-4250-b949-66247f623c3d@suse.cz \
    --to=vbabka@suse.cz \
    --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=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --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