Blame view
mm/Kconfig.debug
6.17 KB
ec8f24b7f treewide: Add SPD... |
1 |
# SPDX-License-Identifier: GPL-2.0-only |
eefa864b7 mm/page_ext: resu... |
2 3 |
config PAGE_EXTENSION bool "Extend memmap on extra space for more information on page" |
a7f7f6248 treewide: replace... |
4 |
help |
eefa864b7 mm/page_ext: resu... |
5 6 7 8 9 |
Extend memmap on extra space for more information on page. This could be used for debugging features that need to insert extra field for every page. This extension enables us to save memory by not allocating this extra memory according to boottime configuration. |
ee3b4290a generic debug pag... |
10 11 |
config DEBUG_PAGEALLOC bool "Debug page memory allocations" |
7bc32f6f9 mm: debug-pageall... |
12 13 |
depends on DEBUG_KERNEL depends on !HIBERNATION || ARCH_SUPPORTS_DEBUG_PAGEALLOC && !PPC && !SPARC |
7bc32f6f9 mm: debug-pageall... |
14 |
select PAGE_POISONING if !ARCH_SUPPORTS_DEBUG_PAGEALLOC |
a7f7f6248 treewide: replace... |
15 |
help |
ee3b4290a generic debug pag... |
16 |
Unmap pages from the kernel linear mapping after free_pages(). |
ea6eabb05 mm/debug_pageallo... |
17 18 |
Depending on runtime enablement, this results in a small or large slowdown, but helps to find certain types of memory corruption. |
ee3b4290a generic debug pag... |
19 |
|
4462b32c9 mm, page_alloc: m... |
20 21 22 |
Also, the state of page tracking structures is checked more often as pages are being allocated and freed, as unexpected state changes often happen for same reasons as memory corruption (e.g. double free, |
8974558f4 mm, page_owner, d... |
23 24 25 |
use-after-free). The error reports for these checks can be augmented with stack traces of last allocation and freeing of the page, when PAGE_OWNER is also selected and enabled on boot. |
4462b32c9 mm, page_alloc: m... |
26 |
|
7bc32f6f9 mm: debug-pageall... |
27 28 |
For architectures which don't enable ARCH_SUPPORTS_DEBUG_PAGEALLOC, fill the pages with poison patterns after free_pages() and verify |
4462b32c9 mm, page_alloc: m... |
29 30 31 32 |
the patterns before alloc_pages(). Additionally, this option cannot be enabled in combination with hibernation as that would result in incorrect warnings of memory corruption after a resume because free pages are not saved to the suspend image. |
7bc32f6f9 mm: debug-pageall... |
33 |
|
ea6eabb05 mm/debug_pageallo... |
34 35 36 37 38 39 40 41 |
By default this option will have a small overhead, e.g. by not allowing the kernel mapping to be backed by large pages on some architectures. Even bigger overhead comes when the debugging is enabled by DEBUG_PAGEALLOC_ENABLE_DEFAULT or the debug_pagealloc command line parameter. config DEBUG_PAGEALLOC_ENABLE_DEFAULT bool "Enable debug page memory allocations by default?" |
ea6eabb05 mm/debug_pageallo... |
42 |
depends on DEBUG_PAGEALLOC |
a7f7f6248 treewide: replace... |
43 |
help |
ea6eabb05 mm/debug_pageallo... |
44 45 |
Enable debug page memory allocations by default? This value can be overridden by debug_pagealloc=off|on. |
8aa49762d mm/page_owner: mo... |
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 |
config PAGE_OWNER bool "Track page owner" depends on DEBUG_KERNEL && STACKTRACE_SUPPORT select DEBUG_FS select STACKTRACE select STACKDEPOT select PAGE_EXTENSION help This keeps track of what call chain is the owner of a page, may help to find bare alloc_page(s) leaks. Even if you include this feature on your build, it is disabled in default. You should pass "page_owner=on" to boot parameter in order to enable it. Eats a fair amount of memory if enabled. See tools/vm/page_owner_sort.c for user-space helper. If unsure, say N. |
6a11f75b6 generic debug pag... |
62 |
config PAGE_POISONING |
8823b1dbc mm/page_poison.c:... |
63 |
bool "Poison pages after freeing" |
8823b1dbc mm/page_poison.c:... |
64 |
select PAGE_POISONING_NO_SANITY if HIBERNATION |
a7f7f6248 treewide: replace... |
65 |
help |
8823b1dbc mm/page_poison.c:... |
66 67 68 |
Fill the pages with poison patterns after free_pages() and verify the patterns before alloc_pages. The filling of the memory helps reduce the risk of information leaks from freed data. This does |
8c9a134ca mm: clarify CONFI... |
69 70 |
have a potential performance impact if enabled with the "page_poison=1" kernel boot option. |
8823b1dbc mm/page_poison.c:... |
71 72 73 74 75 76 77 78 79 |
Note that "poison" here is not the same thing as the "HWPoison" for CONFIG_MEMORY_FAILURE. This is software poisoning only. If unsure, say N config PAGE_POISONING_NO_SANITY depends on PAGE_POISONING bool "Only poison, don't sanity check" |
a7f7f6248 treewide: replace... |
80 |
help |
8823b1dbc mm/page_poison.c:... |
81 82 83 84 85 86 |
Skip the sanity checking on alloc, only fill the pages with poison on free. This reduces some of the overhead of the poisoning feature. If you are only interested in sanitization, say Y. Otherwise say N. |
1414c7f4f mm/page_poisoning... |
87 88 |
config PAGE_POISONING_ZERO |
8c9a134ca mm: clarify CONFI... |
89 |
bool "Use zero for poisoning instead of debugging value" |
1414c7f4f mm/page_poisoning... |
90 |
depends on PAGE_POISONING |
a7f7f6248 treewide: replace... |
91 |
help |
1414c7f4f mm/page_poisoning... |
92 93 94 95 96 |
Instead of using the existing poison value, fill the pages with zeros. This makes it harder to detect when errors are occurring due to sanitization but the zeroing at free means that it is no longer necessary to write zeros when GFP_ZERO is used on allocation. |
1414c7f4f mm/page_poisoning... |
97 |
If unsure, say N |
95813b8fa mm/page_ref: add ... |
98 99 100 101 102 |
config DEBUG_PAGE_REF bool "Enable tracepoint to track down page reference manipulation" depends on DEBUG_KERNEL depends on TRACEPOINTS |
a7f7f6248 treewide: replace... |
103 |
help |
95813b8fa mm/page_ref: add ... |
104 105 106 107 108 109 |
This is a feature to add tracepoint for tracking down page reference manipulation. This tracking is useful to diagnose functional failure due to migration failures caused by page reference mismatches. Be careful when enabling this feature because it adds about 30 KB to the kernel code. However the runtime performance overhead is virtually nil until the tracepoints are actually enabled. |
2959a5f72 mm: add arch-inde... |
110 111 112 113 |
config DEBUG_RODATA_TEST bool "Testcase for the marking rodata read-only" depends on STRICT_KERNEL_RWX |
a7f7f6248 treewide: replace... |
114 |
help |
2959a5f72 mm: add arch-inde... |
115 |
This option enables a testcase for the setting rodata read-only. |
30d621f67 mm: add generic p... |
116 |
|
375d315cb mm: add DEBUG_WX ... |
117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 |
config ARCH_HAS_DEBUG_WX bool config DEBUG_WX bool "Warn on W+X mappings at boot" depends on ARCH_HAS_DEBUG_WX depends on MMU select PTDUMP_CORE help Generate a warning if any W+X mappings are found at boot. This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk. Look for a message in dmesg output like this: <arch>/mm: Checked W+X mappings: passed, no W+X pages found. or like this, if the check failed: <arch>/mm: Checked W+X mappings: failed, <N> W+X pages found. Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier. There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check. If in doubt, say "Y". |
30d621f67 mm: add generic p... |
148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 |
config GENERIC_PTDUMP bool config PTDUMP_CORE bool config PTDUMP_DEBUGFS bool "Export kernel pagetable layout to userspace via debugfs" depends on DEBUG_KERNEL depends on DEBUG_FS depends on GENERIC_PTDUMP select PTDUMP_CORE help Say Y here if you want to show the kernel pagetable layout in a debugfs file. This information is only useful for kernel developers who are working in architecture specific areas of the kernel. It is probably not a good idea to enable this feature in a production kernel. If in doubt, say N. |