Alexander Potapenko 3429055f04 mm: kmsan: implement kmsan_memmove() ... Provide a hook that can be used by custom memcpy implementations to tell KMSAN that the metadata needs to be copied. Without that, false positive reports are possible in the cases where KMSAN fails to intercept memory initialization. Link: https://lore.kernel.org/all/3b7dbd88-0861-4638-b2d2-911c97a4cadf@I-love.SAKURA.ne.jp/ Link: https://lkml.kernel.org/r/20240320101851.2589698-1-glider@google.com Signed-off-by: Alexander Potapenko <glider@google.com> Suggested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Reviewed-by: Marco Elver <elver@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>		2024-04-25 21:07:02 -07: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: implement kmsan_memmove()	2024-04-25 21:07:02 -07: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_test.c	kmsan: introduce test_memcpy_initialized_gap()	2023-10-04 10:32:22 -07:00
kmsan.h
Makefile
report.c
shadow.c	mm: kmsan: panic on failure to allocate early boot metadata	2023-10-25 16:47:10 -07:00