linux/mm/kasan
Andrey Konovalov 1c61990d37 kasan: fix bad call to unpoison_slab_object
Commit 29d7355a9d ("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).

Link: https://lkml.kernel.org/r/20240614143238.60323-1-andrey.konovalov@linux.dev
Fixes: 29d7355a9d ("kasan: save alloc stack traces for mempool")
Signed-off-by: Andrey Konovalov <andreyknvl@gmail.com>
Reported-by: Brad Spengler <spender@grsecurity.net>
Acked-by: Marco Elver <elver@google.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2024-06-24 20:52:09 -07:00
..
common.c kasan: fix bad call to unpoison_slab_object 2024-06-24 20:52:09 -07:00
generic.c slab changes for 6.9 2024-03-12 20:14:54 -07:00
hw_tags.c fix missing vmalloc.h includes 2024-04-25 20:55:49 -07:00
init.c
kasan_test_module.c
kasan_test.c kasan: fix a2 allocation and remove explicit cast in atomic tests 2024-03-04 17:01:17 -08:00
kasan.h
Makefile
quarantine.c
report_generic.c
report_hw_tags.c
report_sw_tags.c
report_tags.c
report.c
shadow.c mm/kasan: use pXd_leaf() in shadow_mapped() 2024-03-06 13:04:19 -08:00
sw_tags.c
tags.c