diff options
| author | Dmitry Vyukov <[email protected]> | 2016-12-12 16:44:53 -0800 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2016-12-12 18:55:09 -0800 |
| commit | 5c5c1f36cedfb51ec291181e71817f7fe7e03ee2 (patch) | |
| tree | 566b1a80fda44dc6997967a0f35335750610f929 | |
| parent | 49920d28781dcced10cd30cb9a938e7d045a1c94 (diff) | |
kasan: support panic_on_warn
If user sets panic_on_warn, he wants kernel to panic if there is
anything barely wrong with the kernel. KASAN-detected errors are
definitely not less benign than an arbitrary kernel WARNING.
Panic after KASAN errors if panic_on_warn is set.
We use this for continuous fuzzing where we want kernel to stop and
reboot on any error.
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Dmitry Vyukov <[email protected]>
Acked-by: Andrey Ryabinin <[email protected]>
Cc: Alexander Potapenko <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
| -rw-r--r-- | mm/kasan/report.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/mm/kasan/report.c b/mm/kasan/report.c index 073325aedc68..b82b3e215157 100644 --- a/mm/kasan/report.c +++ b/mm/kasan/report.c @@ -136,6 +136,8 @@ static void kasan_end_report(unsigned long *flags) pr_err("==================================================================\n"); add_taint(TAINT_BAD_PAGE, LOCKDEP_NOW_UNRELIABLE); spin_unlock_irqrestore(&report_lock, *flags); + if (panic_on_warn) + panic("panic_on_warn set ...\n"); kasan_enable_current(); } |