From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Harry Yoo <harry@kernel.org>, Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Conor Dooley <conor@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev@googlegroups.com,
"Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Subject: [PATCH v3 01/10] slab, kunit: pin test slabs by an extra allocation
Date: Thu, 05 Nov 2026 09:43:50 +0100 [thread overview]
Message-ID: <20261105-slub_tiny_rework-v3-1-0484ce59eabb@kernel.org> (raw)
In-Reply-To: <20261105-slub_tiny_rework-v3-0-0484ce59eabb@kernel.org>
Several of slab kunit tests allocate and free a single object from the
test cache, perform intentional UAF actions and validation, while
expecting the empty slab to stay on the partial list.
This subtly relies on non-zero s->min_partial. It currently compile-time
defaults to a non-zero value, but in theory a sysfs write racing with
the kunit test could change it. More importantly, the upcoming
CONFIG_SLUB_TINY changes will make it possible to run the kunit tests
with s->min_partial being a compile-time zero, which means the tests
will now do unintended UAF writes on the page allocator level, and also
report failures, as flagged by sashiko [1].
To prevent this in a robust way, add an extra object allocation to the
tests, that will prevent the slab being freed. Use migrate_disable() to
prevent migration to a different NUMA node, which would place the
allocation to a different slab.
[1] https://sashiko.dev/#/patchset/20261024-slub_tiny_rework-v2-0-bf1419ab5ffd@kernel.org?part=8
Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
---
lib/tests/slub_kunit.c | 36 ++++++++++++++++++++++++++++++++----
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/lib/tests/slub_kunit.c b/lib/tests/slub_kunit.c
index e3b63f0338d5..40427f7edf4c 100644
--- a/lib/tests/slub_kunit.c
+++ b/lib/tests/slub_kunit.c
@@ -51,10 +51,16 @@ static void test_next_pointer(struct kunit *test)
{
struct kmem_cache *s = test_kmem_cache_create("TestSlub_next_ptr_free",
64, SLAB_POISON);
- u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
+ void *pin;
+ u8 *p;
unsigned long tmp;
unsigned long *ptr_addr;
+ migrate_disable();
+ pin = kmem_cache_alloc(s, GFP_KERNEL);
+ p = kmem_cache_alloc(s, GFP_KERNEL);
+ migrate_enable();
+
kmem_cache_free(s, p);
ptr_addr = (unsigned long *)(p + s->offset);
@@ -89,6 +95,7 @@ static void test_next_pointer(struct kunit *test)
validate_slab_cache(s);
KUNIT_EXPECT_EQ(test, 0, slab_errors);
+ kmem_cache_free(s, pin);
kmem_cache_destroy(s);
}
@@ -96,7 +103,13 @@ static void test_first_word(struct kunit *test)
{
struct kmem_cache *s = test_kmem_cache_create("TestSlub_1th_word_free",
64, SLAB_POISON);
- u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
+ void *pin;
+ u8 *p;
+
+ migrate_disable();
+ pin = kmem_cache_alloc(s, GFP_KERNEL);
+ p = kmem_cache_alloc(s, GFP_KERNEL);
+ migrate_enable();
kmem_cache_free(s, p);
*p = 0x78;
@@ -104,6 +117,7 @@ static void test_first_word(struct kunit *test)
validate_slab_cache(s);
KUNIT_EXPECT_EQ(test, 2, slab_errors);
+ kmem_cache_free(s, pin);
kmem_cache_destroy(s);
}
@@ -111,7 +125,13 @@ static void test_clobber_50th_byte(struct kunit *test)
{
struct kmem_cache *s = test_kmem_cache_create("TestSlub_50th_word_free",
64, SLAB_POISON);
- u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
+ void *pin;
+ u8 *p;
+
+ migrate_disable();
+ pin = kmem_cache_alloc(s, GFP_KERNEL);
+ p = kmem_cache_alloc(s, GFP_KERNEL);
+ migrate_enable();
kmem_cache_free(s, p);
p[50] = 0x9a;
@@ -119,6 +139,7 @@ static void test_clobber_50th_byte(struct kunit *test)
validate_slab_cache(s);
KUNIT_EXPECT_EQ(test, 2, slab_errors);
+ kmem_cache_free(s, pin);
kmem_cache_destroy(s);
}
#endif
@@ -127,7 +148,13 @@ static void test_clobber_redzone_free(struct kunit *test)
{
struct kmem_cache *s = test_kmem_cache_create("TestSlub_RZ_free", 64,
SLAB_RED_ZONE);
- u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
+ void *pin;
+ u8 *p;
+
+ migrate_disable();
+ pin = kmem_cache_alloc(s, GFP_KERNEL);
+ p = kmem_cache_alloc(s, GFP_KERNEL);
+ migrate_enable();
kasan_disable_current();
kmem_cache_free(s, p);
@@ -137,6 +164,7 @@ static void test_clobber_redzone_free(struct kunit *test)
KUNIT_EXPECT_EQ(test, 2, slab_errors);
kasan_enable_current();
+ kmem_cache_free(s, pin);
kmem_cache_destroy(s);
}
--
2.56.0
next prev parent reply other threads:[~2026-11-05 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 8:43 [PATCH v3 00/10] replace CONFIG_SLUB_TINY with a slab_tiny boot parameter Vlastimil Babka (SUSE)
2026-11-05 8:43 ` Vlastimil Babka (SUSE) [this message]
2026-11-05 12:59 ` [PATCH v3 01/10] slab, kunit: pin test slabs by an extra allocation Harry Yoo
2026-11-05 8:43 ` [PATCH v3 02/10] kasan, " Vlastimil Babka (SUSE)
2026-11-05 13:03 ` Harry Yoo
2026-11-05 8:43 ` [PATCH v3 03/10] mm, slab: refactor slab_min/max_order handling Vlastimil Babka (SUSE)
2026-11-05 13:12 ` Harry Yoo
2026-11-05 8:43 ` [PATCH v3 04/10] mm, slab: introduce slab_debug=N Vlastimil Babka (SUSE)
2026-11-05 14:30 ` Harry Yoo
2026-11-05 14:36 ` Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 05/10] mm, slab: rework KMALLOC_RECLAIM handling of SLUB_TINY Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 06/10] mm, slab: make SLUB_TINY handling dynamic for sizing decisions Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 07/10] mm, slab: convert CONFIG_SLUB_TINY checks to kmem_cache_debug() Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 08/10] mm, slab: remove remaining compile-time checks for CONFIG_SLUB_TINY Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 09/10] mm, slab: add slab_tiny boot param Vlastimil Babka (SUSE)
2026-11-05 8:43 ` [PATCH v3 10/10] mm, slab: deprecate CONFIG_SLUB_TINY and reduce its Kconfig effects Vlastimil Babka (SUSE)
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=20261105-slub_tiny_rework-v3-1-0484ce59eabb@kernel.org \
--to=vbabka@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=cl@gentwo.org \
--cc=conor@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.com \
/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®