[merged] kasan-support-panic_on_warn.patch removed from -mm tree

[merged] kasan-support-panic_on_warn.patch removed from -mm tree

[akpm]

The patch titled
     Subject: kasan: support panic_on_warn
has been removed from the -mm tree.  Its filename was
     kasan-support-panic_on_warn.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Dmitry Vyukov <dvyukov@google.com>
Subject: 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/1476694764-31986-1-git-send-email-dvyukov@google.com
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Alexander Potapenko <glider@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/kasan/report.c |    2 ++
 1 file changed, 2 insertions(+)

diff -puN mm/kasan/report.c~kasan-support-panic_on_warn mm/kasan/report.c
--- a/mm/kasan/report.c~kasan-support-panic_on_warn
+++ a/mm/kasan/report.c
@@ -136,6 +136,8 @@ static void kasan_end_report(unsigned lo
 	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();
 }
 
_

Patches currently in -mm which might be from dvyukov@google.com are