Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Hoffmann <f3lix.dev@gmx.de>
To: Harry Yoo <harry@kernel.org>
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 11:09:54 +0100	[thread overview]
Message-ID: <20261114100954.8262-1-f3lix.dev@gmx.de> (raw)
In-Reply-To: <179462737686.1463521.17920259642574913474@kernel.org>

Hi Harry,

Thank you for catching this. You're right: CONFIG_SLAB_VIRTUAL is not in
mainline.

This patch is against the public, out-of-tree SLAB_VIRTUAL feature branch:

https://github.com/thejh/linux/tree/slub-virtual-v7.2

I tested it on commit 699594e8888d (slub-virtual-v7.2-rc5), and confirmed
that the same issue is present in slub-virtual-v7.2. I intended the fix
for the feature authors to fold into a future revision of their series.

I failed to state that dependency in the subject and body, so the
standalone email misleadingly looked like a patch against upstream. That
was my mistake, sorry for the confusion.

Jann, Matteo, and Tamas, please let me know if you would prefer the fix
in a differently labeled or rebased form.

Thanks,
Felix


  reply	other threads:[~2026-11-14 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 22:13 [PATCH] mm/slub: Flush virtual-slab work before cache destruction Felix Hoffmann
2026-11-14  3:38 ` Harry Yoo
2026-11-14 10:09   ` Felix Hoffmann [this message]
2026-11-14 22:14 ` sashiko-bot

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=20261114100954.8262-1-f3lix.dev@gmx.de \
    --to=f3lix.dev@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=hao.li@linux.dev \
    --cc=harry@kernel.org \
    --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