Alexander Potapenko 2ef3cec44c kmsan: do not wipe out origin when doing partial unpoisoning ... As noticed by Brian, KMSAN should not be zeroing the origin when unpoisoning parts of a four-byte uninitialized value, e.g.: char a[4]; kmsan_unpoison_memory(a, 1); This led to false negatives, as certain poisoned values could receive zero origins, preventing those values from being reported. To fix the problem, check that kmsan_internal_set_shadow_origin() writes zero origins only to slots which have zero shadow. Link: https://lkml.kernel.org/r/20240528104807.738758-1-glider@google.com Fixes: f80be4571b ("kmsan: add KMSAN runtime core") Signed-off-by: Alexander Potapenko <glider@google.com> Reported-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com> Link: https://lore.kernel.org/lkml/20240524232804.1984355-1-bjohannesmeyer@gmail.com/T/ Reviewed-by: Marco Elver <elver@google.com> Tested-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com> Cc: Dmitry Vyukov <dvyukov@google.com> Cc: Kees Cook <keescook@chromium.org> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>		2024-06-05 19:19:25 -07:00
..
core.c	kmsan: do not wipe out origin when doing partial unpoisoning	2024-06-05 19:19:25 -07: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	kmsan: disable ftrace in kmsan core code	2023-02-20 12:46:16 -08:00
report.c
shadow.c	mm: kmsan: panic on failure to allocate early boot metadata	2023-10-25 16:47:10 -07:00