summaryrefslogblamecommitdiff
path: root/lib/Kconfig.kasan
blob: 67d8c6838ba95fe244060e1d67362220e646514f (plain) (tree) 
0b24becc810d ^







7ed2f9e66385 ^

bebf56a1b176 ^

cd11016e5f52 ^

0b24becc810d ^



01e76903f655 ^





89d3c87e20d9 ^

7ed2f9e66385 ^


0b24becc810d ^

0b24becc810d ^





















01e76903f655 ^

0b24becc810d ^



3f15801cdc23 ^








0b24becc810d ^

1
2
3
4
5
6
7

8

9

10

11
12
13

14
15
16
17
18

19

20
21

22

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

44

45
46
47

48
49
50
51
52
53
54
55

56







                                             
                                                      
                           
                                 


                                                                          




                                                                              
                                                              

                                                                    
 




















                                                                         
                                                      


         







                                                                          
     
config HAVE_ARCH_KASAN
	bool

if HAVE_ARCH_KASAN

config KASAN
	bool "KASan: runtime memory debugger"
	depends on SLUB_DEBUG || (SLAB && !DEBUG_SLAB)
	select CONSTRUCTORS
	select STACKDEPOT if SLAB
	help
	  Enables kernel address sanitizer - runtime memory debugger,
	  designed to find out-of-bounds accesses and use-after-free bugs.
	  This is strictly a debugging feature and it requires a gcc version
	  of 4.9.2 or later. Detection of out of bounds accesses to stack or
	  global variables requires gcc 5.0 or later.
	  This feature consumes about 1/8 of available memory and brings about
	  ~x3 performance slowdown.
	  For better error detection enable CONFIG_STACKTRACE.
	  Currently CONFIG_KASAN doesn't work with CONFIG_DEBUG_SLAB
	  (the resulting kernel does not boot).

choice
	prompt "Instrumentation type"
	depends on KASAN
	default KASAN_OUTLINE

config KASAN_OUTLINE
	bool "Outline instrumentation"
	help
	  Before every memory access compiler insert function call
	  __asan_load*/__asan_store*. These functions performs check
	  of shadow memory. This is slower than inline instrumentation,
	  however it doesn't bloat size of kernel's .text section so
	  much as inline does.

config KASAN_INLINE
	bool "Inline instrumentation"
	help
	  Compiler directly inserts code checking shadow memory before
	  memory accesses. This is faster than outline (in some workloads
	  it gives about x2 boost over outline instrumentation), but
	  make kernel's .text size much bigger.
	  This requires a gcc version of 5.0 or later.

endchoice

config TEST_KASAN
	tristate "Module for testing kasan for bug detection"
	depends on m && KASAN
	help
	  This is a test module doing various nasty things like
	  out of bounds accesses, use after free. It is useful for testing
	  kernel debugging features like kernel address sanitizer.

endif