Andrey Ryabinin eb06f43f1c kasan: always taint kernel on report ... Currently we already taint the kernel in some cases. E.g. if we hit some bug in slub memory we call object_err() which will taint the kernel with TAINT_BAD_PAGE flag. But for other kind of bugs kernel left untainted. Always taint with TAINT_BAD_PAGE if kasan found some bug. This is useful for automated testing. Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com> Cc: Alexander Potapenko <glider@google.com> Reviewed-by: Dmitry Vyukov <dvyukov@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2015-11-05 19:34:48 -08:00
..
kasan_init.c	x86/kasan, mm: Introduce generic kasan_populate_zero_shadow()	2015-08-22 14:54:55 +02:00
kasan.c	kasan: use IS_ALIGNED in memory_is_poisoned_8()	2015-11-05 19:34:48 -08:00
kasan.h	kasan: update reported bug types for not user nor kernel memory accesses	2015-11-05 19:34:48 -08:00
Makefile	x86/kasan, mm: Introduce generic kasan_populate_zero_shadow()	2015-08-22 14:54:55 +02:00
report.c	kasan: always taint kernel on report	2015-11-05 19:34:48 -08:00