Lines Matching refs:a
18 Depending on runtime enablement, this results in a small or large
32 incorrect warnings of memory corruption after a resume because free
35 By default this option will have a small overhead, e.g. by not
70 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
77 # without KASAN, so mark it as a dependency of KASAN for now.
90 Unfortunately this also prevents a very specific bug pattern from
93 KASAN builds, in case you want to test for such a bug.
100 This is designed as a debugging feature, not a security feature.
113 This keeps track of what call chain is the owner of a page, may
117 a fair amount of memory if enabled. See tools/mm/page_owner_sort.c
153 have a potential performance impact if enabled with the
170 This is a feature to add tracepoint for tracking down page reference
181 This option enables a testcase for the setting rodata read-only.
193 Generate a warning if any W+X mappings are found at boot.
196 mappings after applying NX, as such mappings are a security risk.
198 Look for a message in dmesg output like this:
207 still fine, as W+X mappings are not a security hole in
212 once the kernel has booted up - it's a one time check.
229 Say Y here if you want to show the kernel pagetable layout in a
232 It is probably not a good idea to enable this feature in a production
251 detector. The memory allocation/freeing is traced in a way
273 freed before kmemleak is fully initialised, use a static pool
308 identify pathological cases. Counting these events introduces a small