Commit b0845ce5 authored by Mark Rutland's avatar Mark Rutland Committed by Linus Torvalds
Browse files

kasan: report only the first error by default

Disable kasan after the first report.  There are several reasons for

 - Single bug quite often has multiple invalid memory accesses causing
   storm in the dmesg.

 - Write OOB access might corrupt metadata so the next report will print
   bogus alloc/free stacktraces.

 - Reports after the first easily could be not bugs by itself but just
   side effects of the first one.

Given that multiple reports usually only do harm, it makes sense to
disable kasan after the first one.  If user wants to see all the
reports, the boot-time parameter kasan_multi_shot must be used.

[ wrote changelog and doc, added missing include]

Signed-off-by: Mark Rutland's avatarMark Rutland <>
Signed-off-by: default avatarAndrey Ryabinin <>
Cc: Andrey Konovalov <>
Cc: Alexander Potapenko <>
Cc: Dmitry Vyukov <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent 4742a35d
......@@ -1725,6 +1725,12 @@
kernel and module base offset ASLR (Address Space
Layout Randomization).
[KNL] Enforce KASAN (Kernel Address Sanitizer) to print
report on every invalid memory access. Without this
parameter KASAN will print report only for the first
invalid access.
keepinitrd [HW,ARM]
kernelcore= [KNL,X86,IA-64,PPC]
......@@ -76,6 +76,9 @@ size_t ksize(const void *);
static inline void kasan_unpoison_slab(const void *ptr) { ksize(ptr); }
size_t kasan_metadata_size(struct kmem_cache *cache);
bool kasan_save_enable_multi_shot(void);
void kasan_restore_multi_shot(bool enabled);
#else /* CONFIG_KASAN */
static inline void kasan_unpoison_shadow(const void *address, size_t size) {}
......@@ -20,6 +20,7 @@
#include <linux/string.h>
#include <linux/uaccess.h>
#include <linux/module.h>
#include <linux/kasan.h>
* Note: test functions are marked noinline so that their names appear in
......@@ -474,6 +475,12 @@ static noinline void __init use_after_scope_test(void)
static int __init kmalloc_tests_init(void)
* Temporarily enable multi-shot mode. Otherwise, we'd only get a
* report for the first case.
bool multishot = kasan_save_enable_multi_shot();
......@@ -499,6 +506,9 @@ static int __init kmalloc_tests_init(void)
return -EAGAIN;
......@@ -96,11 +96,6 @@ static inline const void *kasan_shadow_to_mem(const void *shadow_addr)
static inline bool kasan_report_enabled(void)
return !current->kasan_depth;
void kasan_report(unsigned long addr, size_t size,
bool is_write, unsigned long ip);
void kasan_report_double_free(struct kmem_cache *cache, void *object,
......@@ -13,7 +13,9 @@
#include <linux/bitops.h>
#include <linux/ftrace.h>
#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/mm.h>
#include <linux/printk.h>
......@@ -293,6 +295,40 @@ static void kasan_report_error(struct kasan_access_info *info)
static unsigned long kasan_flags;
bool kasan_save_enable_multi_shot(void)
return test_and_set_bit(KASAN_BIT_MULTI_SHOT, &kasan_flags);
void kasan_restore_multi_shot(bool enabled)
if (!enabled)
clear_bit(KASAN_BIT_MULTI_SHOT, &kasan_flags);
static int __init kasan_set_multi_shot(char *str)
set_bit(KASAN_BIT_MULTI_SHOT, &kasan_flags);
return 1;
__setup("kasan_multi_shot", kasan_set_multi_shot);
static inline bool kasan_report_enabled(void)
if (current->kasan_depth)
return false;
if (test_bit(KASAN_BIT_MULTI_SHOT, &kasan_flags))
return true;
return !test_and_set_bit(KASAN_BIT_REPORTED, &kasan_flags);
void kasan_report(unsigned long addr, size_t size,
bool is_write, unsigned long ip)
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment