kasan-fix-bad-call-to-unpoison_slab_object.patch removed from -mm tree
The quilt patch titled
Subject: kasan: fix bad call to unpoison_slab_object
has been removed from the -mm tree. Its filename was
kasan-fix-bad-call-to-unpoison_slab_object.patch
This patch was dropped because it was merged into the mm-hotfixes-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Andrey Konovalov <[email protected]>
Subject: kasan: fix bad call to unpoison_slab_object
Date: Fri, 14 Jun 2024 16:32:38 +0200
Commit 29d7355a9d05 ("kasan: save alloc stack traces for mempool") messed up one of the calls to unpoison_slab_object: the last two arguments are supposed to be GFP flags and whether to init the object memory.
Fix the call.
Without this fix, __kasan_mempool_unpoison_object provides the object's size as GFP flags to unpoison_slab_object, which can cause LOCKDEP reports (and probably other issues).
---
mm/kasan/common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/kasan/common.c renamed from mm/kasan/common.c~kasan-fix-bad-call-to-unpoison_slab_object +1 -1
@@ -532,7 +532,7 @@ void __kasan_mempool_unpoison_object(voireturn ;/* Unpoison the object and save alloc info for non-kmalloc() allocations. */ -unpoison_slab_object (slab->slab_cache, ptr, size, flags); +unpoison_slab_object (slab->slab_cache, ptr, flags, false);/* Poison the redzone and save alloc info for kmalloc() allocations. */ if (is_kmalloc_cache (slab->slab_cache))
_
Patches currently in -mm which might be from [email protected] are