Aneesh Kumar K.V fc5aeeaf59 mm/kasan: prevent deadlock in kasan reporting ... When we end up calling kasan_report in real mode, our shadow mapping for the spinlock variable will show poisoned. This will result in us calling kasan_report_error with lock_report spin lock held. To prevent this disable kasan reporting when we are priting error w.r.t kasan. Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> Reviewed-by: Andrey Ryabinin <ryabinin.a.a@gmail.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: fix last shadow judgement in memory_is_poisoned_16()	2015-09-17 21:16:07 -07:00
kasan.h	mm/kasan: rename kasan_enabled() to kasan_report_enabled()	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	mm/kasan: prevent deadlock in kasan reporting	2015-11-05 19:34:48 -08:00