linux/mm/kfence
Alexander Potapenko f2b84d2e40 kfence: use error_report_end tracepoint
Make it possible to trace KFENCE 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-3-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: Vlastimil Babka <vbabka@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2021-02-26 09:41:02 -08:00
..
core.c kfence: report sensitive information based on no_hash_pointers 2021-02-26 09:41:02 -08:00
kfence_test.c kfence: report sensitive information based on no_hash_pointers 2021-02-26 09:41:02 -08:00
kfence.h kfence: report sensitive information based on no_hash_pointers 2021-02-26 09:41:02 -08:00
Makefile kfence: add test suite 2021-02-26 09:41:02 -08:00
report.c kfence: use error_report_end tracepoint 2021-02-26 09:41:02 -08:00