Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1501789
| From | Dmitry Vyukov <dvyukov@google.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH] kasan: support panic_on_warn |
| Date | 2016-10-17 11:00 +0200 |
| Message-ID | <stbW2-1d0-15@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Cc: kasan-dev@googlegroups.com
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
---
Changes from v1:
- don't reset panic_on_warn before calling panic()
---
mm/kasan/report.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/kasan/report.c b/mm/kasan/report.c
index 24c1211..0ee8211 100644
--- a/mm/kasan/report.c
+++ b/mm/kasan/report.c
@@ -133,6 +133,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();
}
--
2.8.0.rc3.226.g39d4020
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH] kasan: support panic_on_warn Dmitry Vyukov <dvyukov@google.com> - 2016-10-17 11:00 +0200
csiph-web