7 bool "KASan: runtime memory debugger"
11 Enables kernel address sanitizer - runtime memory debugger,
12 designed to find out-of-bounds accesses and use-after-free bugs.
13 This is strictly a debugging feature and it requires a gcc version
14 of 4.9.2 or later. Detection of out of bounds accesses to stack or
15 global variables requires gcc 5.0 or later.
16 This feature consumes about 1/8 of available memory and brings about
17 ~x3 performance slowdown.
18 For better error detection enable CONFIG_STACKTRACE,
19 and add slub_debug=U to boot cmdline.
22 prompt "Instrumentation type"
27 bool "Outline instrumentation"
29 Before every memory access compiler insert function call
30 __asan_load*/__asan_store*. These functions performs check
31 of shadow memory. This is slower than inline instrumentation,
32 however it doesn't bloat size of kernel's .text section so
36 bool "Inline instrumentation"
38 Compiler directly inserts code checking shadow memory before
39 memory accesses. This is faster than outline (in some workloads
40 it gives about x2 boost over outline instrumentation), but
41 make kernel's .text size much bigger.
42 This requires a gcc version of 5.0 or later.
47 tristate "Module for testing kasan for bug detection"
50 This is a test module doing various nasty things like
51 out of bounds accesses, use after free. It is useful for testing
52 kernel debugging features like kernel address sanitizer.