From: Harry Yoo <harry@kernel.org>
To: Felix Hoffmann <f3lix.dev@gmx.de>
Cc: Jann Horn <jannh@google.com>,
Matteo Rizzo <matteorizzo@google.com>,
Tamas Koczka <poprdi@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
linux-mm@kvack.org, Kees Cook <kees@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slub: Flush virtual-slab work before cache destruction
Date: Sat, 14 Nov 2026 03:38:25 +0000 [thread overview]
Message-ID: <179462737686.1463521.17920259642574913474@kernel.org> (raw)
In-Reply-To: <20261113221330.162567-1-f3lix.dev@gmx.de>
Hi Felix,
CONFIG_SLAB_VIRTUAL is not in the upstream kernel.
Maybe you sent a patch for a downstream tree to the upstream?
On Fri, 13 Nov 2026 23:13:30 +0100, Felix Hoffmann wrote:
> Under CONFIG_SLAB_VIRTUAL, freeing a slab queues it to
> slub_tlbflush_work. The worker later follows slab->slab_cache to take the
> cache's virtual-slab lock and update its lists.
>
> __kmem_cache_shutdown() can report success after the last slabs have been
> removed from the cache's accounting but before that deferred work runs.
> The cache can then be released while queued slabs still refer to it. When
> the worker runs, it dereferences the freed kmem_cache and corrupts its
> lists.
>
> Flush the virtual-slab worker after confirming that every cache node is
> empty and before allowing cache destruction to proceed. This drains both
> queued and running work that can still reference the cache.
>
> Fixes: 0d6f38b78adda ("mm/slub: allocate slabs from virtual memory")
> Signed-off-by: Felix Hoffmann <f3lix.dev@gmx.de>
> ---
> Tested on x86-64 with KCSAN enabled:
>
> - on the unmodified SLAB_VIRTUAL feature kernel, a stress module that
> repeatedly created, filled, emptied and destroyed a non-mergeable cache
> triggered list corruption in slub_tlbflush_worker() and panicked the
> kernel almost immediately
> - with this change, the identical module completed 10,000 cache
> create/destroy cycles (81.92 million allocation/free pairs) without a
> BUG, warning, KCSAN report or panic
> - the fixed KCSAN kernel and the external stress module build with W=1
>
> The reproducer and complete console logs are available privately on request.
> mm/slub.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index b4c64b2bbd334..dbfd42b31a0a2 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -8541,6 +8541,11 @@ int __kmem_cache_shutdown(struct kmem_cache *s)
> if (n->nr_partial || node_nr_slabs(n))
> return 1;
> }
> +
> +#ifdef CONFIG_SLAB_VIRTUAL
> + /* The TLB flush worker still dereferences slab->slab_cache. */
> + kthread_flush_work(&slub_tlbflush_work);
> +#endif
> return 0;
> }
>
> --
> 2.43.0
prev parent reply other threads:[~2026-11-14 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 22:13 Felix Hoffmann
2026-11-14 3:38 ` Harry Yoo [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=179462737686.1463521.17920259642574913474@kernel.org \
--to=harry@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=f3lix.dev@gmx.de \
--cc=hao.li@linux.dev \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matteorizzo@google.com \
--cc=poprdi@google.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@kernel.org \
/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
all inboxes | Powered by JetHome®