Alexander Potapenko d749cc7547 mm: kmsan: remove runtime checks from kmsan_unpoison_memory() ... Similarly to what's been done in commit 85716a80c1 ("kmsan: allow using __msan_instrument_asm_store() inside runtime"), it should be safe to call kmsan_unpoison_memory() from within the runtime, as it does not allocate memory or take locks. Remove the redundant runtime checks. This should fix false positives seen with CONFIG_DEBUG_LIST=y when the non-instrumented lib/stackdepot.c failed to unpoison the memory chunks later checked by the instrumented lib/list_debug.c Also replace the implementation of kmsan_unpoison_entry_regs() with a call to kmsan_unpoison_memory(). Link: https://lkml.kernel.org/r/20240124173134.1165747-1-glider@google.com Fixes: f80be4571b ("kmsan: add KMSAN runtime core") Signed-off-by: Alexander Potapenko <glider@google.com> Tested-by: Marco Elver <elver@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Cc: Ilya Leoshkevich <iii@linux.ibm.com> Cc: Nicholas Miehlbradt <nicholas@linux.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>		2024-02-22 10:24:41 -08:00
..
Makefile	kmsan: disable ftrace in kmsan core code	2023-02-20 12:46:16 -08:00
core.c	kmsan: use stack_depot_save instead of __stack_depot_save	2023-12-10 16:51:46 -08:00
hooks.c	mm: kmsan: remove runtime checks from kmsan_unpoison_memory()	2024-02-22 10:24:41 -08:00
init.c	mm, treewide: rename MAX_ORDER to MAX_PAGE_ORDER	2024-01-08 15:27:15 -08:00
instrumentation.c	kasan,kmsan: remove __GFP_KSWAPD_RECLAIM usage from kasan/kmsan	2023-06-23 16:59:26 -07:00
kmsan.h	kmsan: core: kmsan_in_runtime() should return true in NMI context	2022-11-08 15:57:24 -08:00
kmsan_test.c	kmsan: introduce test_memcpy_initialized_gap()	2023-10-04 10:32:22 -07:00
report.c	…
shadow.c	mm: kmsan: panic on failure to allocate early boot metadata	2023-10-25 16:47:10 -07:00