Lines Matching +full:no +full:- +full:insert +full:- +full:detect

1 # SPDX-License-Identifier: GPL-2.0-only
23 	def_bool $(cc-option, -fsanitize=kernel-address)
26 	def_bool $(cc-option, -fsanitize=kernel-hwaddress)
43 	  Enables KASAN (Kernel Address Sanitizer) - a dynamic memory safety
44 	  error detector designed to find out-of-bounds and use-after-free bugs.
46 	  See Documentation/dev-tools/kasan.rst for details.
53 …def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=kernel-address -mllvm -asan-kernel-mem-intrinsic-p…
54 		 (CC_IS_GCC && $(cc-option,-fsanitize=kernel-address --param asan-kernel-mem-intrinsic-prefix=1))
69 	  2. Software Tag-Based KASAN (arm64 only, based on software memory
72 	  3. Hardware Tag-Based KASAN (arm64 only, based on hardware memory
75 	  See Documentation/dev-tools/kasan.rst for details about each mode.
93 	bool "Software Tag-Based KASAN"
99 	  Enables Software Tag-Based KASAN.
112 	bool "Hardware Tag-Based KASAN"
115 	  Enables Hardware Tag-Based KASAN.
137 	  Makes the compiler insert function calls that check whether the memory
145 	  Makes the compiler directly insert memory accessibility checks before
157 	  Disables stack instrumentation and thus KASAN's ability to detect
158 	  out-of-bounds bugs in stack variables.
164 	  This option is always disabled when compile-testing with Clang to
171 	  as well, as it adds inline-style instrumentation that is run
183 	  With Hardware Tag-Based KASAN, only non-executable VM_ALLOC mappings
184 	  are checked. There is no additional memory usage.
187 	tristate "KUnit-compatible tests of KASAN bug detection capabilities" if !KUNIT_ALL_TESTS
191 	  A KUnit-based KASAN test suite. Triggers different kinds of
192 	  out-of-bounds and use-after-free accesses. Useful for testing whether
193 	  KASAN can detect certain bug types.
196 	  to the KUnit documentation in Documentation/dev-tools/kunit/.
210 	  In Generic KASAN, each kmalloc-8 and kmalloc-16 object will add
211 	  16 bytes of additional memory consumption, and each kmalloc-32