Lines Matching +full:mode +full:- +full:based
1 # SPDX-License-Identifier: GPL-2.0-only
2 # This config refers to the generic KASAN mode.
13 def_bool $(cc-option, -fsanitize=kernel-address)
16 def_bool $(cc-option, -fsanitize=kernel-hwaddress)
28 Enables KASAN (KernelAddressSANitizer) - runtime memory debugger,
29 designed to find out-of-bounds accesses and use-after-free bugs.
30 See Documentation/dev-tools/kasan.rst for details.
35 prompt "KASAN mode"
40 software tag-based KASAN (a version based on software memory
44 Both generic and tag-based KASAN are strictly debugging features.
47 bool "Generic mode"
54 Enables generic KASAN mode.
56 This mode is supported in both GCC and Clang. With GCC it requires
58 but detection of out-of-bounds accesses for global variables is
61 This mode consumes about 1/8th of available memory at kernel start
71 bool "Software tag-based mode"
78 Enables software tag-based KASAN mode.
80 This mode requires Top Byte Ignore support by the CPU and therefore
81 is only supported for arm64. This mode requires Clang.
83 This mode consumes about 1/16th of available memory at kernel start
85 This mode may potentially introduce problems relating to pointer
127 Disabling asan-stack makes it safe to run kernels build
128 with clang-8 with KASAN enabled, though it loses some of
130 This feature is always disabled when compile-testing with clang
142 bool "KASan: use 4-level paging"
145 Compiling the kernel with KASan disables automatic 3-level vs
146 4-level paging selection. 3-level paging is used by default (up
148 4-level paging instead.
154 This option enables best-effort identification of bug type
155 (use-after-free or out-of-bounds) at the cost of increased
162 By default, the shadow region for vmalloc space is the read-only
172 tristate "KUnit-compatible tests of KASAN bug detection capabilities" if !KUNIT_ALL_TESTS
181 to the KUnit documentation in Documentation/dev-tools/kunit
184 tristate "KUnit-incompatible tests of KASAN bug detection capabilities"