Revision d3a61f745e0d089a2484740283a434deb6dd4eb5 authored by Alexander Potapenko on 26 February 2021, 01:19:51 UTC, committed by Linus Torvalds on 26 February 2021, 17:41:02 UTC
Make it possible to trace KASAN error reporting.  A good usecase is
watching for trace events from the userspace to detect and process memory
corruption reports from the kernel.

Link: https://lkml.kernel.org/r/20210121131915.1331302-4-glider@google.com
Signed-off-by: Alexander Potapenko <glider@google.com>
Suggested-by: Marco Elver <elver@google.com>
Cc: Andrey Konovalov <andreyknvl@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent f2b84d2
History
File Mode Size
boot
configs
include
kernel
lib
math-emu
mm
Kconfig -rw-r--r-- 9.9 KB
Kconfig.debug -rw-r--r-- 78 bytes
Makefile -rw-r--r-- 5.4 KB
defpalo.conf -rw-r--r-- 815 bytes
install.sh -rw-r--r-- 1.6 KB
nm -rw-r--r-- 194 bytes

back to top