Commit | Line | Data |
---|---|---|
06ec64b8 CH |
1 | menu "Kernel hacking" |
2 | ||
604ff0dc | 3 | menu "printk and dmesg options" |
1da177e4 LT |
4 | |
5 | config PRINTK_TIME | |
6 | bool "Show timing information on printks" | |
d3b8b6e5 | 7 | depends on PRINTK |
1da177e4 | 8 | help |
649e6ee3 KS |
9 | Selecting this option causes time stamps of the printk() |
10 | messages to be added to the output of the syslog() system | |
11 | call and at the console. | |
12 | ||
13 | The timestamp is always recorded internally, and exported | |
14 | to /dev/kmsg. This flag just specifies if the timestamp should | |
15 | be included, not that the timestamp is recorded. | |
16 | ||
17 | The behavior is also controlled by the kernel command line | |
8c27ceff | 18 | parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst |
1da177e4 | 19 | |
a8cfdc68 OJ |
20 | config CONSOLE_LOGLEVEL_DEFAULT |
21 | int "Default console loglevel (1-15)" | |
22 | range 1 15 | |
23 | default "7" | |
24 | help | |
25 | Default loglevel to determine what will be printed on the console. | |
26 | ||
27 | Setting a default here is equivalent to passing in loglevel=<x> in | |
28 | the kernel bootargs. loglevel=<x> continues to override whatever | |
29 | value is specified here as well. | |
30 | ||
50f4d9bd | 31 | Note: This does not affect the log level of un-prefixed printk() |
a8cfdc68 OJ |
32 | usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT |
33 | option. | |
34 | ||
42a9dc0b | 35 | config MESSAGE_LOGLEVEL_DEFAULT |
5af5bcb8 MSB |
36 | int "Default message log level (1-7)" |
37 | range 1 7 | |
38 | default "4" | |
39 | help | |
40 | Default log level for printk statements with no specified priority. | |
41 | ||
42 | This was hard-coded to KERN_WARNING since at least 2.6.10 but folks | |
43 | that are auditing their logs closely may want to set it to a lower | |
44 | priority. | |
45 | ||
a8cfdc68 OJ |
46 | Note: This does not affect what message level gets printed on the console |
47 | by default. To change that, use loglevel=<x> in the kernel bootargs, | |
48 | or pick a different CONSOLE_LOGLEVEL_DEFAULT configuration value. | |
49 | ||
604ff0dc DH |
50 | config BOOT_PRINTK_DELAY |
51 | bool "Delay each boot printk message by N milliseconds" | |
52 | depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY | |
53 | help | |
54 | This build option allows you to read kernel boot messages | |
55 | by inserting a short delay after each one. The delay is | |
56 | specified in milliseconds on the kernel command line, | |
57 | using "boot_delay=N". | |
58 | ||
59 | It is likely that you would also need to use "lpj=M" to preset | |
60 | the "loops per jiffie" value. | |
61 | See a previous boot log for the "lpj" value to use for your | |
62 | system, and then set "lpj=M" before setting "boot_delay=N". | |
63 | NOTE: Using this option may adversely affect SMP systems. | |
64 | I.e., processors other than the first one may not boot up. | |
65 | BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect | |
66 | what it believes to be lockup conditions. | |
67 | ||
68 | config DYNAMIC_DEBUG | |
69 | bool "Enable dynamic printk() support" | |
70 | default n | |
71 | depends on PRINTK | |
72 | depends on DEBUG_FS | |
73 | help | |
74 | ||
75 | Compiles debug level messages into the kernel, which would not | |
76 | otherwise be available at runtime. These messages can then be | |
77 | enabled/disabled based on various levels of scope - per source file, | |
78 | function, module, format string, and line number. This mechanism | |
79 | implicitly compiles in all pr_debug() and dev_dbg() calls, which | |
80 | enlarges the kernel text size by about 2%. | |
81 | ||
82 | If a source file is compiled with DEBUG flag set, any | |
83 | pr_debug() calls in it are enabled by default, but can be | |
84 | disabled at runtime as below. Note that DEBUG flag is | |
85 | turned on by many CONFIG_*DEBUG* options. | |
86 | ||
87 | Usage: | |
88 | ||
89 | Dynamic debugging is controlled via the 'dynamic_debug/control' file, | |
90 | which is contained in the 'debugfs' filesystem. Thus, the debugfs | |
91 | filesystem must first be mounted before making use of this feature. | |
92 | We refer the control file as: <debugfs>/dynamic_debug/control. This | |
93 | file contains a list of the debug statements that can be enabled. The | |
94 | format for each line of the file is: | |
95 | ||
96 | filename:lineno [module]function flags format | |
97 | ||
98 | filename : source file of the debug statement | |
99 | lineno : line number of the debug statement | |
100 | module : module that contains the debug statement | |
101 | function : function that contains the debug statement | |
102 | flags : '=p' means the line is turned 'on' for printing | |
103 | format : the format used for the debug statement | |
104 | ||
105 | From a live system: | |
106 | ||
107 | nullarbor:~ # cat <debugfs>/dynamic_debug/control | |
108 | # filename:lineno [module]function flags format | |
109 | fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012" | |
110 | fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012" | |
111 | fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012" | |
112 | ||
113 | Example usage: | |
114 | ||
115 | // enable the message at line 1603 of file svcsock.c | |
116 | nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' > | |
117 | <debugfs>/dynamic_debug/control | |
118 | ||
119 | // enable all the messages in file svcsock.c | |
120 | nullarbor:~ # echo -n 'file svcsock.c +p' > | |
121 | <debugfs>/dynamic_debug/control | |
122 | ||
123 | // enable all the messages in the NFS server module | |
124 | nullarbor:~ # echo -n 'module nfsd +p' > | |
125 | <debugfs>/dynamic_debug/control | |
126 | ||
127 | // enable all 12 messages in the function svc_process() | |
128 | nullarbor:~ # echo -n 'func svc_process +p' > | |
129 | <debugfs>/dynamic_debug/control | |
130 | ||
131 | // disable all 12 messages in the function svc_process() | |
132 | nullarbor:~ # echo -n 'func svc_process -p' > | |
133 | <debugfs>/dynamic_debug/control | |
134 | ||
f8998c22 HH |
135 | See Documentation/admin-guide/dynamic-debug-howto.rst for additional |
136 | information. | |
604ff0dc DH |
137 | |
138 | endmenu # "printk and dmesg options" | |
139 | ||
6dfc0665 DH |
140 | menu "Compile-time checks and compiler options" |
141 | ||
142 | config DEBUG_INFO | |
143 | bool "Compile the kernel with debug info" | |
12b13835 | 144 | depends on DEBUG_KERNEL && !COMPILE_TEST |
6dfc0665 DH |
145 | help |
146 | If you say Y here the resulting kernel image will include | |
147 | debugging info resulting in a larger kernel image. | |
148 | This adds debug symbols to the kernel and modules (gcc -g), and | |
149 | is needed if you intend to use kernel crashdump or binary object | |
150 | tools like crash, kgdb, LKCD, gdb, etc on the kernel. | |
151 | Say Y here only if you plan to debug the kernel. | |
152 | ||
153 | If unsure, say N. | |
154 | ||
155 | config DEBUG_INFO_REDUCED | |
156 | bool "Reduce debugging information" | |
157 | depends on DEBUG_INFO | |
158 | help | |
159 | If you say Y here gcc is instructed to generate less debugging | |
160 | information for structure types. This means that tools that | |
161 | need full debugging information (like kgdb or systemtap) won't | |
162 | be happy. But if you merely need debugging information to | |
163 | resolve line numbers there is no loss. Advantage is that | |
164 | build directory object sizes shrink dramatically over a full | |
165 | DEBUG_INFO build and compile times are reduced too. | |
166 | Only works with newer gcc versions. | |
167 | ||
866ced95 AK |
168 | config DEBUG_INFO_SPLIT |
169 | bool "Produce split debuginfo in .dwo files" | |
a687a533 | 170 | depends on DEBUG_INFO |
866ced95 AK |
171 | help |
172 | Generate debug info into separate .dwo files. This significantly | |
173 | reduces the build directory size for builds with DEBUG_INFO, | |
174 | because it stores the information only once on disk in .dwo | |
175 | files instead of multiple times in object files and executables. | |
176 | In addition the debug information is also compressed. | |
177 | ||
178 | Requires recent gcc (4.7+) and recent gdb/binutils. | |
179 | Any tool that packages or reads debug information would need | |
180 | to know about the .dwo files and include them. | |
181 | Incompatible with older versions of ccache. | |
182 | ||
bfaf2dd3 AK |
183 | config DEBUG_INFO_DWARF4 |
184 | bool "Generate dwarf4 debuginfo" | |
185 | depends on DEBUG_INFO | |
186 | help | |
187 | Generate dwarf4 debug info. This requires recent versions | |
188 | of gcc and gdb. It makes the debug information larger. | |
189 | But it significantly improves the success of resolving | |
190 | variables in gdb on optimized code. | |
191 | ||
3ee7b3fa JK |
192 | config GDB_SCRIPTS |
193 | bool "Provide GDB scripts for kernel debugging" | |
194 | depends on DEBUG_INFO | |
195 | help | |
196 | This creates the required links to GDB helper scripts in the | |
197 | build directory. If you load vmlinux into gdb, the helper | |
198 | scripts will be automatically imported by gdb as well, and | |
199 | additional functions are available to analyze a Linux kernel | |
700199b0 AP |
200 | instance. See Documentation/dev-tools/gdb-kernel-debugging.rst |
201 | for further details. | |
3ee7b3fa | 202 | |
de488443 JG |
203 | config ENABLE_WARN_DEPRECATED |
204 | bool "Enable __deprecated logic" | |
205 | default y | |
206 | help | |
207 | Enable the __deprecated logic in the kernel build. | |
208 | Disable this to suppress the "warning: 'foo' is deprecated | |
209 | (declared at kernel/power/somefile.c:1234)" messages. | |
210 | ||
cebc04ba AM |
211 | config ENABLE_MUST_CHECK |
212 | bool "Enable __must_check logic" | |
213 | default y | |
214 | help | |
215 | Enable the __must_check logic in the kernel build. Disable this to | |
216 | suppress the "warning: ignoring return value of 'foo', declared with | |
217 | attribute warn_unused_result" messages. | |
1da177e4 | 218 | |
35bb5b1e AK |
219 | config FRAME_WARN |
220 | int "Warn for stack frames larger than (needs gcc 4.4)" | |
221 | range 0 8192 | |
e7c52b84 | 222 | default 3072 if KASAN_EXTRA |
0e07f663 | 223 | default 2048 if GCC_PLUGIN_LATENT_ENTROPY |
432654df HD |
224 | default 1280 if (!64BIT && PARISC) |
225 | default 1024 if (!64BIT && !PARISC) | |
35bb5b1e AK |
226 | default 2048 if 64BIT |
227 | help | |
228 | Tell gcc to warn at build time for stack frames larger than this. | |
229 | Setting this too low will cause a lot of warnings. | |
230 | Setting it to 0 disables the warning. | |
231 | Requires gcc 4.4 | |
232 | ||
99657c78 RD |
233 | config STRIP_ASM_SYMS |
234 | bool "Strip assembler-generated symbols during link" | |
235 | default n | |
236 | help | |
237 | Strip internal assembler-generated symbols during a link (symbols | |
238 | that look like '.Lxxx') so they don't pollute the output of | |
239 | get_wchan() and suchlike. | |
240 | ||
1873e870 AK |
241 | config READABLE_ASM |
242 | bool "Generate readable assembler code" | |
243 | depends on DEBUG_KERNEL | |
244 | help | |
245 | Disable some compiler optimizations that tend to generate human unreadable | |
246 | assembler output. This may make the kernel slightly slower, but it helps | |
247 | to keep kernel developers who have to stare a lot at assembler listings | |
248 | sane. | |
249 | ||
f71d20e9 AV |
250 | config UNUSED_SYMBOLS |
251 | bool "Enable unused/obsolete exported symbols" | |
252 | default y if X86 | |
253 | help | |
254 | Unused but exported symbols make the kernel needlessly bigger. For | |
255 | that reason most of these unused exports will soon be removed. This | |
256 | option is provided temporarily to provide a transition period in case | |
257 | some external kernel module needs one of these symbols anyway. If you | |
258 | encounter such a case in your module, consider if you are actually | |
259 | using the right API. (rationale: since nobody in the kernel is using | |
260 | this in a module, there is a pretty good chance it's actually the | |
261 | wrong interface to use). If you really need the symbol, please send a | |
262 | mail to the linux kernel mailing list mentioning the symbol and why | |
263 | you really need it, and what the merge plan to the mainline kernel for | |
264 | your module is. | |
265 | ||
48c96a36 JK |
266 | config PAGE_OWNER |
267 | bool "Track page owner" | |
268 | depends on DEBUG_KERNEL && STACKTRACE_SUPPORT | |
269 | select DEBUG_FS | |
270 | select STACKTRACE | |
f2ca0b55 | 271 | select STACKDEPOT |
48c96a36 JK |
272 | select PAGE_EXTENSION |
273 | help | |
274 | This keeps track of what call chain is the owner of a page, may | |
275 | help to find bare alloc_page(s) leaks. Even if you include this | |
276 | feature on your build, it is disabled in default. You should pass | |
277 | "page_owner=on" to boot parameter in order to enable it. Eats | |
278 | a fair amount of memory if enabled. See tools/vm/page_owner_sort.c | |
279 | for user-space helper. | |
280 | ||
281 | If unsure, say N. | |
282 | ||
bf4735a4 DM |
283 | config DEBUG_FS |
284 | bool "Debug Filesystem" | |
bf4735a4 DM |
285 | help |
286 | debugfs is a virtual file system that kernel developers use to put | |
287 | debugging files into. Enable this option to be able to read and | |
288 | write to these files. | |
289 | ||
ff543332 | 290 | For detailed documentation on the debugfs API, see |
e1b4fc7a | 291 | Documentation/filesystems/. |
ff543332 | 292 | |
bf4735a4 DM |
293 | If unsure, say N. |
294 | ||
295 | config HEADERS_CHECK | |
296 | bool "Run 'make headers_check' when building vmlinux" | |
297 | depends on !UML | |
298 | help | |
299 | This option will extract the user-visible kernel headers whenever | |
300 | building the kernel, and will run basic sanity checks on them to | |
301 | ensure that exported files do not attempt to include files which | |
302 | were not exported, etc. | |
303 | ||
304 | If you're making modifications to header files which are | |
305 | relevant for userspace, say 'Y', and check the headers | |
306 | exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in | |
307 | your build tree), to make sure they're suitable. | |
308 | ||
91341d4b SR |
309 | config DEBUG_SECTION_MISMATCH |
310 | bool "Enable full Section mismatch analysis" | |
91341d4b SR |
311 | help |
312 | The section mismatch analysis checks if there are illegal | |
313 | references from one section to another section. | |
e809ab01 MW |
314 | During linktime or runtime, some sections are dropped; |
315 | any use of code/data previously in these sections would | |
91341d4b | 316 | most likely result in an oops. |
e809ab01 | 317 | In the code, functions and variables are annotated with |
0db0628d | 318 | __init,, etc. (see the full list in include/linux/init.h), |
d6fbfa4f | 319 | which results in the code/data being placed in specific sections. |
e809ab01 MW |
320 | The section mismatch analysis is always performed after a full |
321 | kernel build, and enabling this option causes the following | |
322 | additional steps to occur: | |
323 | - Add the option -fno-inline-functions-called-once to gcc commands. | |
324 | When inlining a function annotated with __init in a non-init | |
325 | function, we would lose the section information and thus | |
91341d4b | 326 | the analysis would not catch the illegal reference. |
e809ab01 MW |
327 | This option tells gcc to inline less (but it does result in |
328 | a larger kernel). | |
f49821ee | 329 | - Run the section mismatch analysis for each module/built-in.a file. |
e809ab01 | 330 | When we run the section mismatch analysis on vmlinux.o, we |
67797b92 | 331 | lose valuable information about where the mismatch was |
91341d4b | 332 | introduced. |
f49821ee | 333 | Running the analysis for each module/built-in.a file |
e809ab01 MW |
334 | tells where the mismatch happens much closer to the |
335 | source. The drawback is that the same mismatch is | |
336 | reported at least twice. | |
337 | - Enable verbose reporting from modpost in order to help resolve | |
338 | the section mismatches that are reported. | |
91341d4b | 339 | |
47490ec1 NB |
340 | config SECTION_MISMATCH_WARN_ONLY |
341 | bool "Make section mismatch errors non-fatal" | |
342 | default y | |
343 | help | |
344 | If you say N here, the build process will fail if there are any | |
345 | section mismatch, instead of just throwing warnings. | |
346 | ||
347 | If unsure, say Y. | |
348 | ||
6dfc0665 DH |
349 | # |
350 | # Select this config option from the architecture Kconfig, if it | |
351 | # is preferred to always offer frame pointers as a config | |
352 | # option on the architecture (regardless of KERNEL_DEBUG): | |
353 | # | |
354 | config ARCH_WANT_FRAME_POINTERS | |
355 | bool | |
f346f4b3 | 356 | |
6dfc0665 DH |
357 | config FRAME_POINTER |
358 | bool "Compile the kernel with frame pointers" | |
a687a533 | 359 | depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS |
6dfc0665 | 360 | default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS |
a304e1b8 | 361 | help |
6dfc0665 DH |
362 | If you say Y here the resulting kernel image will be slightly |
363 | larger and slower, but it gives very useful debugging information | |
364 | in case of kernel bugs. (precise oopses/stacktraces/warnings) | |
a304e1b8 | 365 | |
b9ab5ebb JP |
366 | config STACK_VALIDATION |
367 | bool "Compile-time stack metadata validation" | |
368 | depends on HAVE_STACK_VALIDATION | |
369 | default n | |
370 | help | |
371 | Add compile-time checks to validate stack metadata, including frame | |
372 | pointers (if CONFIG_FRAME_POINTER is enabled). This helps ensure | |
373 | that runtime stack traces are more reliable. | |
374 | ||
ee9f8fce | 375 | This is also a prerequisite for generation of ORC unwind data, which |
11af8474 | 376 | is needed for CONFIG_UNWINDER_ORC. |
ee9f8fce | 377 | |
b9ab5ebb JP |
378 | For more information, see |
379 | tools/objtool/Documentation/stack-validation.txt. | |
380 | ||
6dfc0665 DH |
381 | config DEBUG_FORCE_WEAK_PER_CPU |
382 | bool "Force weak per-cpu definitions" | |
383 | depends on DEBUG_KERNEL | |
8446f1d3 | 384 | help |
6dfc0665 DH |
385 | s390 and alpha require percpu variables in modules to be |
386 | defined weak to work around addressing range issue which | |
387 | puts the following two restrictions on percpu variable | |
388 | definitions. | |
8446f1d3 | 389 | |
6dfc0665 DH |
390 | 1. percpu symbols must be unique whether static or not |
391 | 2. percpu variables can't be defined inside a function | |
8446f1d3 | 392 | |
6dfc0665 DH |
393 | To ensure that generic code follows the above rules, this |
394 | option forces all percpu variables to be defined as weak. | |
5f329089 | 395 | |
6dfc0665 | 396 | endmenu # "Compiler options" |
8446f1d3 | 397 | |
6dfc0665 DH |
398 | config MAGIC_SYSRQ |
399 | bool "Magic SysRq key" | |
400 | depends on !UML | |
401 | help | |
402 | If you say Y here, you will have some control over the system even | |
403 | if the system crashes for example during kernel debugging (e.g., you | |
404 | will be able to flush the buffer cache to disk, reboot the system | |
405 | immediately or dump some status information). This is accomplished | |
406 | by pressing various keys while holding SysRq (Alt+PrintScreen). It | |
407 | also works on a serial console (on PC hardware at least), if you | |
408 | send a BREAK and then within 5 seconds a command keypress. The | |
f8998c22 HH |
409 | keys are documented in <file:Documentation/admin-guide/sysrq.rst>. |
410 | Don't say Y unless you really know what this hack does. | |
8446f1d3 | 411 | |
8eaede49 BH |
412 | config MAGIC_SYSRQ_DEFAULT_ENABLE |
413 | hex "Enable magic SysRq key functions by default" | |
414 | depends on MAGIC_SYSRQ | |
415 | default 0x1 | |
416 | help | |
417 | Specifies which SysRq key functions are enabled by default. | |
418 | This may be set to 1 or 0 to enable or disable them all, or | |
f8998c22 | 419 | to a bitmask as described in Documentation/admin-guide/sysrq.rst. |
8eaede49 | 420 | |
732dbf3a FF |
421 | config MAGIC_SYSRQ_SERIAL |
422 | bool "Enable magic SysRq key over serial" | |
423 | depends on MAGIC_SYSRQ | |
424 | default y | |
425 | help | |
426 | Many embedded boards have a disconnected TTL level serial which can | |
427 | generate some garbage that can lead to spurious false sysrq detects. | |
428 | This option allows you to decide whether you want to enable the | |
429 | magic SysRq key. | |
430 | ||
f346f4b3 AB |
431 | config DEBUG_KERNEL |
432 | bool "Kernel debugging" | |
fef2c9bc | 433 | help |
f346f4b3 AB |
434 | Say Y here if you are developing drivers or trying to debug and |
435 | identify kernel problems. | |
fef2c9bc | 436 | |
0610c8a8 | 437 | menu "Memory Debugging" |
fef2c9bc | 438 | |
0610c8a8 | 439 | source mm/Kconfig.debug |
fef2c9bc | 440 | |
0610c8a8 DH |
441 | config DEBUG_OBJECTS |
442 | bool "Debug object operations" | |
443 | depends on DEBUG_KERNEL | |
9c44bc03 | 444 | help |
0610c8a8 DH |
445 | If you say Y here, additional code will be inserted into the |
446 | kernel to track the life time of various objects and validate | |
447 | the operations on those objects. | |
9c44bc03 | 448 | |
0610c8a8 DH |
449 | config DEBUG_OBJECTS_SELFTEST |
450 | bool "Debug objects selftest" | |
451 | depends on DEBUG_OBJECTS | |
452 | help | |
453 | This enables the selftest of the object debug code. | |
9c44bc03 | 454 | |
0610c8a8 DH |
455 | config DEBUG_OBJECTS_FREE |
456 | bool "Debug objects in freed memory" | |
457 | depends on DEBUG_OBJECTS | |
458 | help | |
459 | This enables checks whether a k/v free operation frees an area | |
460 | which contains an object which has not been deactivated | |
461 | properly. This can make kmalloc/kfree-intensive workloads | |
462 | much slower. | |
3ac7fe5a | 463 | |
c6f3a97f TG |
464 | config DEBUG_OBJECTS_TIMERS |
465 | bool "Debug timer objects" | |
466 | depends on DEBUG_OBJECTS | |
467 | help | |
468 | If you say Y here, additional code will be inserted into the | |
469 | timer routines to track the life time of timer objects and | |
470 | validate the timer operations. | |
471 | ||
dc186ad7 TG |
472 | config DEBUG_OBJECTS_WORK |
473 | bool "Debug work objects" | |
474 | depends on DEBUG_OBJECTS | |
475 | help | |
476 | If you say Y here, additional code will be inserted into the | |
477 | work queue routines to track the life time of work objects and | |
478 | validate the work operations. | |
479 | ||
551d55a9 MD |
480 | config DEBUG_OBJECTS_RCU_HEAD |
481 | bool "Debug RCU callbacks objects" | |
fc2ecf7e | 482 | depends on DEBUG_OBJECTS |
551d55a9 MD |
483 | help |
484 | Enable this to turn on debugging of RCU list heads (call_rcu() usage). | |
485 | ||
e2852ae8 TH |
486 | config DEBUG_OBJECTS_PERCPU_COUNTER |
487 | bool "Debug percpu counter objects" | |
488 | depends on DEBUG_OBJECTS | |
489 | help | |
490 | If you say Y here, additional code will be inserted into the | |
491 | percpu counter routines to track the life time of percpu counter | |
492 | objects and validate the percpu counter operations. | |
493 | ||
3ae70205 IM |
494 | config DEBUG_OBJECTS_ENABLE_DEFAULT |
495 | int "debug_objects bootup default value (0-1)" | |
496 | range 0 1 | |
497 | default "1" | |
498 | depends on DEBUG_OBJECTS | |
499 | help | |
500 | Debug objects boot parameter default value | |
501 | ||
1da177e4 | 502 | config DEBUG_SLAB |
4a2f0acf | 503 | bool "Debug slab memory allocations" |
4675ff05 | 504 | depends on DEBUG_KERNEL && SLAB |
1da177e4 LT |
505 | help |
506 | Say Y here to have the kernel do limited verification on memory | |
507 | allocation as well as poisoning memory on free to catch use of freed | |
508 | memory. This can make kmalloc/kfree-intensive workloads much slower. | |
509 | ||
871751e2 AV |
510 | config DEBUG_SLAB_LEAK |
511 | bool "Memory leak debugging" | |
512 | depends on DEBUG_SLAB | |
513 | ||
f0630fff CL |
514 | config SLUB_DEBUG_ON |
515 | bool "SLUB debugging on by default" | |
4675ff05 | 516 | depends on SLUB && SLUB_DEBUG |
f0630fff CL |
517 | default n |
518 | help | |
519 | Boot with debugging on by default. SLUB boots by default with | |
520 | the runtime debug capabilities switched off. Enabling this is | |
521 | equivalent to specifying the "slub_debug" parameter on boot. | |
522 | There is no support for more fine grained debug control like | |
523 | possible with slub_debug=xxx. SLUB debugging may be switched | |
524 | off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying | |
525 | "slub_debug=-". | |
526 | ||
8ff12cfc CL |
527 | config SLUB_STATS |
528 | default n | |
529 | bool "Enable SLUB performance statistics" | |
ab4d5ed5 | 530 | depends on SLUB && SYSFS |
8ff12cfc CL |
531 | help |
532 | SLUB statistics are useful to debug SLUBs allocation behavior in | |
533 | order find ways to optimize the allocator. This should never be | |
534 | enabled for production use since keeping statistics slows down | |
535 | the allocator by a few percentage points. The slabinfo command | |
536 | supports the determination of the most active slabs to figure | |
537 | out which slabs are relevant to a particular load. | |
538 | Try running: slabinfo -DA | |
539 | ||
b69ec42b CM |
540 | config HAVE_DEBUG_KMEMLEAK |
541 | bool | |
542 | ||
3bba00d7 CM |
543 | config DEBUG_KMEMLEAK |
544 | bool "Kernel memory leak detector" | |
525c1f92 | 545 | depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK |
79e0d9bd | 546 | select DEBUG_FS |
3bba00d7 CM |
547 | select STACKTRACE if STACKTRACE_SUPPORT |
548 | select KALLSYMS | |
b60e26a2 | 549 | select CRC32 |
3bba00d7 CM |
550 | help |
551 | Say Y here if you want to enable the memory leak | |
552 | detector. The memory allocation/freeing is traced in a way | |
553 | similar to the Boehm's conservative garbage collector, the | |
554 | difference being that the orphan objects are not freed but | |
555 | only shown in /sys/kernel/debug/kmemleak. Enabling this | |
556 | feature will introduce an overhead to memory | |
700199b0 | 557 | allocations. See Documentation/dev-tools/kmemleak.rst for more |
3bba00d7 CM |
558 | details. |
559 | ||
0610c8a8 DH |
560 | Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances |
561 | of finding leaks due to the slab objects poisoning. | |
562 | ||
563 | In order to access the kmemleak file, debugfs needs to be | |
564 | mounted (usually at /sys/kernel/debug). | |
565 | ||
566 | config DEBUG_KMEMLEAK_EARLY_LOG_SIZE | |
567 | int "Maximum kmemleak early log entries" | |
568 | depends on DEBUG_KMEMLEAK | |
569 | range 200 40000 | |
570 | default 400 | |
571 | help | |
572 | Kmemleak must track all the memory allocations to avoid | |
573 | reporting false positives. Since memory may be allocated or | |
574 | freed before kmemleak is initialised, an early log buffer is | |
575 | used to store these actions. If kmemleak reports "early log | |
576 | buffer exceeded", please increase this value. | |
577 | ||
578 | config DEBUG_KMEMLEAK_TEST | |
579 | tristate "Simple test for the kernel memory leak detector" | |
580 | depends on DEBUG_KMEMLEAK && m | |
581 | help | |
582 | This option enables a module that explicitly leaks memory. | |
583 | ||
584 | If unsure, say N. | |
585 | ||
586 | config DEBUG_KMEMLEAK_DEFAULT_OFF | |
587 | bool "Default kmemleak to off" | |
588 | depends on DEBUG_KMEMLEAK | |
589 | help | |
590 | Say Y here to disable kmemleak by default. It can then be enabled | |
591 | on the command line via kmemleak=on. | |
592 | ||
593 | config DEBUG_STACK_USAGE | |
594 | bool "Stack utilization instrumentation" | |
6c31da34 | 595 | depends on DEBUG_KERNEL && !IA64 |
0610c8a8 DH |
596 | help |
597 | Enables the display of the minimum amount of free stack which each | |
598 | task has ever had available in the sysrq-T and sysrq-P debug output. | |
599 | ||
600 | This option will slow down process creation somewhat. | |
601 | ||
602 | config DEBUG_VM | |
603 | bool "Debug VM" | |
604 | depends on DEBUG_KERNEL | |
605 | help | |
606 | Enable this to turn on extended checks in the virtual-memory system | |
607 | that may impact performance. | |
608 | ||
609 | If unsure, say N. | |
610 | ||
4f115147 DB |
611 | config DEBUG_VM_VMACACHE |
612 | bool "Debug VMA caching" | |
613 | depends on DEBUG_VM | |
614 | help | |
615 | Enable this to turn on VMA caching debug information. Doing so | |
616 | can cause significant overhead, so only enable it in non-production | |
617 | environments. | |
618 | ||
619 | If unsure, say N. | |
620 | ||
0610c8a8 DH |
621 | config DEBUG_VM_RB |
622 | bool "Debug VM red-black trees" | |
623 | depends on DEBUG_VM | |
624 | help | |
a663dad6 | 625 | Enable VM red-black tree debugging information and extra validations. |
0610c8a8 DH |
626 | |
627 | If unsure, say N. | |
628 | ||
95ad9755 KS |
629 | config DEBUG_VM_PGFLAGS |
630 | bool "Debug page-flags operations" | |
631 | depends on DEBUG_VM | |
632 | help | |
633 | Enables extra validation on page flags operations. | |
634 | ||
635 | If unsure, say N. | |
636 | ||
fa5b6ec9 LA |
637 | config ARCH_HAS_DEBUG_VIRTUAL |
638 | bool | |
639 | ||
0610c8a8 DH |
640 | config DEBUG_VIRTUAL |
641 | bool "Debug VM translations" | |
fa5b6ec9 | 642 | depends on DEBUG_KERNEL && ARCH_HAS_DEBUG_VIRTUAL |
0610c8a8 DH |
643 | help |
644 | Enable some costly sanity checks in virtual to page code. This can | |
645 | catch mistakes with virt_to_page() and friends. | |
646 | ||
647 | If unsure, say N. | |
648 | ||
649 | config DEBUG_NOMMU_REGIONS | |
650 | bool "Debug the global anon/private NOMMU mapping region tree" | |
651 | depends on DEBUG_KERNEL && !MMU | |
652 | help | |
653 | This option causes the global tree of anonymous and private mapping | |
654 | regions to be regularly checked for invalid topology. | |
655 | ||
656 | config DEBUG_MEMORY_INIT | |
657 | bool "Debug memory initialisation" if EXPERT | |
658 | default !EXPERT | |
659 | help | |
660 | Enable this for additional checks during memory initialisation. | |
661 | The sanity checks verify aspects of the VM such as the memory model | |
662 | and other information provided by the architecture. Verbose | |
663 | information will be printed at KERN_DEBUG loglevel depending | |
664 | on the mminit_loglevel= command-line option. | |
665 | ||
666 | If unsure, say Y | |
667 | ||
668 | config MEMORY_NOTIFIER_ERROR_INJECT | |
669 | tristate "Memory hotplug notifier error injection module" | |
670 | depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION | |
671 | help | |
672 | This option provides the ability to inject artificial errors to | |
673 | memory hotplug notifier chain callbacks. It is controlled through | |
674 | debugfs interface under /sys/kernel/debug/notifier-error-inject/memory | |
675 | ||
676 | If the notifier call chain should be failed with some events | |
677 | notified, write the error code to "actions/<notifier event>/error". | |
678 | ||
679 | Example: Inject memory hotplug offline error (-12 == -ENOMEM) | |
680 | ||
681 | # cd /sys/kernel/debug/notifier-error-inject/memory | |
682 | # echo -12 > actions/MEM_GOING_OFFLINE/error | |
683 | # echo offline > /sys/devices/system/memory/memoryXXX/state | |
684 | bash: echo: write error: Cannot allocate memory | |
685 | ||
686 | To compile this code as a module, choose M here: the module will | |
687 | be called memory-notifier-error-inject. | |
688 | ||
689 | If unsure, say N. | |
690 | ||
691 | config DEBUG_PER_CPU_MAPS | |
692 | bool "Debug access to per_cpu maps" | |
693 | depends on DEBUG_KERNEL | |
694 | depends on SMP | |
695 | help | |
696 | Say Y to verify that the per_cpu map being accessed has | |
697 | been set up. This adds a fair amount of code to kernel memory | |
698 | and decreases performance. | |
699 | ||
700 | Say N if unsure. | |
701 | ||
702 | config DEBUG_HIGHMEM | |
703 | bool "Highmem debugging" | |
704 | depends on DEBUG_KERNEL && HIGHMEM | |
705 | help | |
b1357c9f GU |
706 | This option enables additional error checking for high memory |
707 | systems. Disable for production systems. | |
0610c8a8 DH |
708 | |
709 | config HAVE_DEBUG_STACKOVERFLOW | |
710 | bool | |
711 | ||
712 | config DEBUG_STACKOVERFLOW | |
713 | bool "Check for stack overflows" | |
714 | depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW | |
715 | ---help--- | |
716 | Say Y here if you want to check for overflows of kernel, IRQ | |
edb0ec07 | 717 | and exception stacks (if your architecture uses them). This |
0610c8a8 DH |
718 | option will show detailed messages if free stack space drops |
719 | below a certain limit. | |
720 | ||
721 | These kinds of bugs usually occur when call-chains in the | |
722 | kernel get too deep, especially when interrupts are | |
723 | involved. | |
724 | ||
725 | Use this in cases where you see apparently random memory | |
726 | corruption, especially if it appears in 'struct thread_info' | |
727 | ||
728 | If in doubt, say "N". | |
729 | ||
0b24becc AR |
730 | source "lib/Kconfig.kasan" |
731 | ||
0610c8a8 DH |
732 | endmenu # "Memory Debugging" |
733 | ||
5c9a8750 DV |
734 | config ARCH_HAS_KCOV |
735 | bool | |
736 | help | |
737 | KCOV does not have any arch-specific code, but currently it is enabled | |
738 | only for x86_64. KCOV requires testing on other archs, and most likely | |
739 | disabling of instrumentation for some early boot code. | |
740 | ||
5aadfdeb MY |
741 | config CC_HAS_SANCOV_TRACE_PC |
742 | def_bool $(cc-option,-fsanitize-coverage=trace-pc) | |
743 | ||
5c9a8750 DV |
744 | config KCOV |
745 | bool "Code coverage for fuzzing" | |
746 | depends on ARCH_HAS_KCOV | |
5aadfdeb | 747 | depends on CC_HAS_SANCOV_TRACE_PC || GCC_PLUGINS |
5c9a8750 | 748 | select DEBUG_FS |
5aadfdeb | 749 | select GCC_PLUGIN_SANCOV if !CC_HAS_SANCOV_TRACE_PC |
5c9a8750 DV |
750 | help |
751 | KCOV exposes kernel code coverage information in a form suitable | |
752 | for coverage-guided fuzzing (randomized testing). | |
753 | ||
754 | If RANDOMIZE_BASE is enabled, PC values will not be stable across | |
755 | different machines and across reboots. If you need stable PC values, | |
756 | disable RANDOMIZE_BASE. | |
757 | ||
700199b0 | 758 | For more details, see Documentation/dev-tools/kcov.rst. |
5c9a8750 | 759 | |
d677a4d6 VC |
760 | config KCOV_ENABLE_COMPARISONS |
761 | bool "Enable comparison operands collection by KCOV" | |
762 | depends on KCOV | |
5aadfdeb | 763 | depends on $(cc-option,-fsanitize-coverage=trace-cmp) |
d677a4d6 VC |
764 | help |
765 | KCOV also exposes operands of every comparison in the instrumented | |
766 | code along with operand sizes and PCs of the comparison instructions. | |
767 | These operands can be used by fuzzing engines to improve the quality | |
768 | of fuzzing coverage. | |
769 | ||
a4691dea VN |
770 | config KCOV_INSTRUMENT_ALL |
771 | bool "Instrument all code by default" | |
772 | depends on KCOV | |
5aadfdeb | 773 | default y |
a4691dea VN |
774 | help |
775 | If you are doing generic system call fuzzing (like e.g. syzkaller), | |
776 | then you will want to instrument the whole kernel and you should | |
777 | say y here. If you are doing more targeted fuzzing (like e.g. | |
778 | filesystem fuzzing with AFL) then you will want to enable coverage | |
779 | for more specific subsets of files, and should say n here. | |
780 | ||
a304e1b8 DW |
781 | config DEBUG_SHIRQ |
782 | bool "Debug shared IRQ handlers" | |
0244ad00 | 783 | depends on DEBUG_KERNEL |
a304e1b8 DW |
784 | help |
785 | Enable this to generate a spurious interrupt as soon as a shared | |
786 | interrupt handler is registered, and just before one is deregistered. | |
787 | Drivers ought to be able to handle interrupts coming in at those | |
788 | points; some don't and need to be caught. | |
789 | ||
92aef8fb DH |
790 | menu "Debug Lockups and Hangs" |
791 | ||
58687acb | 792 | config LOCKUP_DETECTOR |
05a4a952 NP |
793 | bool |
794 | ||
795 | config SOFTLOCKUP_DETECTOR | |
796 | bool "Detect Soft Lockups" | |
dea20a3f | 797 | depends on DEBUG_KERNEL && !S390 |
05a4a952 | 798 | select LOCKUP_DETECTOR |
8446f1d3 | 799 | help |
58687acb | 800 | Say Y here to enable the kernel to act as a watchdog to detect |
05a4a952 | 801 | soft lockups. |
58687acb DZ |
802 | |
803 | Softlockups are bugs that cause the kernel to loop in kernel | |
5f329089 | 804 | mode for more than 20 seconds, without giving other tasks a |
58687acb DZ |
805 | chance to run. The current stack trace is displayed upon |
806 | detection and the system will stay locked up. | |
8446f1d3 | 807 | |
5f00ae0d RD |
808 | config BOOTPARAM_SOFTLOCKUP_PANIC |
809 | bool "Panic (Reboot) On Soft Lockups" | |
810 | depends on SOFTLOCKUP_DETECTOR | |
811 | help | |
812 | Say Y here to enable the kernel to panic on "soft lockups", | |
813 | which are bugs that cause the kernel to loop in kernel | |
814 | mode for more than 20 seconds (configurable using the watchdog_thresh | |
815 | sysctl), without giving other tasks a chance to run. | |
816 | ||
817 | The panic can be used in combination with panic_timeout, | |
818 | to cause the system to reboot automatically after a | |
819 | lockup has been detected. This feature is useful for | |
820 | high-availability systems that have uptime guarantees and | |
821 | where a lockup must be resolved ASAP. | |
822 | ||
823 | Say N if unsure. | |
824 | ||
825 | config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE | |
826 | int | |
827 | depends on SOFTLOCKUP_DETECTOR | |
828 | range 0 1 | |
829 | default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC | |
830 | default 1 if BOOTPARAM_SOFTLOCKUP_PANIC | |
831 | ||
05a4a952 NP |
832 | config HARDLOCKUP_DETECTOR_PERF |
833 | bool | |
834 | select SOFTLOCKUP_DETECTOR | |
835 | ||
7edaeb68 TG |
836 | # |
837 | # Enables a timestamp based low pass filter to compensate for perf based | |
838 | # hard lockup detection which runs too fast due to turbo modes. | |
839 | # | |
840 | config HARDLOCKUP_CHECK_TIMESTAMP | |
841 | bool | |
842 | ||
05a4a952 NP |
843 | # |
844 | # arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard | |
845 | # lockup detector rather than the perf based detector. | |
846 | # | |
847 | config HARDLOCKUP_DETECTOR | |
848 | bool "Detect Hard Lockups" | |
849 | depends on DEBUG_KERNEL && !S390 | |
850 | depends on HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_ARCH | |
851 | select LOCKUP_DETECTOR | |
852 | select HARDLOCKUP_DETECTOR_PERF if HAVE_HARDLOCKUP_DETECTOR_PERF | |
853 | select HARDLOCKUP_DETECTOR_ARCH if HAVE_HARDLOCKUP_DETECTOR_ARCH | |
854 | help | |
855 | Say Y here to enable the kernel to act as a watchdog to detect | |
856 | hard lockups. | |
857 | ||
58687acb | 858 | Hardlockups are bugs that cause the CPU to loop in kernel mode |
5f329089 | 859 | for more than 10 seconds, without letting other interrupts have a |
58687acb DZ |
860 | chance to run. The current stack trace is displayed upon detection |
861 | and the system will stay locked up. | |
8446f1d3 | 862 | |
fef2c9bc DZ |
863 | config BOOTPARAM_HARDLOCKUP_PANIC |
864 | bool "Panic (Reboot) On Hard Lockups" | |
8f1f66ed | 865 | depends on HARDLOCKUP_DETECTOR |
fef2c9bc DZ |
866 | help |
867 | Say Y here to enable the kernel to panic on "hard lockups", | |
868 | which are bugs that cause the kernel to loop in kernel | |
5f329089 FLVC |
869 | mode with interrupts disabled for more than 10 seconds (configurable |
870 | using the watchdog_thresh sysctl). | |
fef2c9bc DZ |
871 | |
872 | Say N if unsure. | |
873 | ||
874 | config BOOTPARAM_HARDLOCKUP_PANIC_VALUE | |
875 | int | |
8f1f66ed | 876 | depends on HARDLOCKUP_DETECTOR |
fef2c9bc DZ |
877 | range 0 1 |
878 | default 0 if !BOOTPARAM_HARDLOCKUP_PANIC | |
879 | default 1 if BOOTPARAM_HARDLOCKUP_PANIC | |
880 | ||
e162b39a MSB |
881 | config DETECT_HUNG_TASK |
882 | bool "Detect Hung Tasks" | |
883 | depends on DEBUG_KERNEL | |
05a4a952 | 884 | default SOFTLOCKUP_DETECTOR |
e162b39a | 885 | help |
0610c8a8 DH |
886 | Say Y here to enable the kernel to detect "hung tasks", |
887 | which are bugs that cause the task to be stuck in | |
96b03ab8 | 888 | uninterruptible "D" state indefinitely. |
1da177e4 | 889 | |
0610c8a8 DH |
890 | When a hung task is detected, the kernel will print the |
891 | current stack trace (which you should report), but the | |
892 | task will stay in uninterruptible state. If lockdep is | |
893 | enabled then all held locks will also be reported. This | |
894 | feature has negligible overhead. | |
871751e2 | 895 | |
0610c8a8 DH |
896 | config DEFAULT_HUNG_TASK_TIMEOUT |
897 | int "Default timeout for hung task detection (in seconds)" | |
898 | depends on DETECT_HUNG_TASK | |
899 | default 120 | |
f0630fff | 900 | help |
0610c8a8 DH |
901 | This option controls the default timeout (in seconds) used |
902 | to determine when a task has become non-responsive and should | |
903 | be considered hung. | |
f0630fff | 904 | |
0610c8a8 DH |
905 | It can be adjusted at runtime via the kernel.hung_task_timeout_secs |
906 | sysctl or by writing a value to | |
907 | /proc/sys/kernel/hung_task_timeout_secs. | |
8ff12cfc | 908 | |
0610c8a8 DH |
909 | A timeout of 0 disables the check. The default is two minutes. |
910 | Keeping the default should be fine in most cases. | |
b69ec42b | 911 | |
0610c8a8 DH |
912 | config BOOTPARAM_HUNG_TASK_PANIC |
913 | bool "Panic (Reboot) On Hung Tasks" | |
914 | depends on DETECT_HUNG_TASK | |
3bba00d7 | 915 | help |
0610c8a8 DH |
916 | Say Y here to enable the kernel to panic on "hung tasks", |
917 | which are bugs that cause the kernel to leave a task stuck | |
918 | in uninterruptible "D" state. | |
3bba00d7 | 919 | |
0610c8a8 DH |
920 | The panic can be used in combination with panic_timeout, |
921 | to cause the system to reboot automatically after a | |
922 | hung task has been detected. This feature is useful for | |
923 | high-availability systems that have uptime guarantees and | |
924 | where a hung tasks must be resolved ASAP. | |
bf96d1e3 | 925 | |
0610c8a8 | 926 | Say N if unsure. |
bf96d1e3 | 927 | |
0610c8a8 DH |
928 | config BOOTPARAM_HUNG_TASK_PANIC_VALUE |
929 | int | |
930 | depends on DETECT_HUNG_TASK | |
931 | range 0 1 | |
932 | default 0 if !BOOTPARAM_HUNG_TASK_PANIC | |
933 | default 1 if BOOTPARAM_HUNG_TASK_PANIC | |
3bba00d7 | 934 | |
82607adc TH |
935 | config WQ_WATCHDOG |
936 | bool "Detect Workqueue Stalls" | |
937 | depends on DEBUG_KERNEL | |
938 | help | |
939 | Say Y here to enable stall detection on workqueues. If a | |
940 | worker pool doesn't make forward progress on a pending work | |
941 | item for over a given amount of time, 30s by default, a | |
942 | warning message is printed along with dump of workqueue | |
943 | state. This can be configured through kernel parameter | |
944 | "workqueue.watchdog_thresh" and its sysfs counterpart. | |
945 | ||
92aef8fb DH |
946 | endmenu # "Debug lockups and hangs" |
947 | ||
948 | config PANIC_ON_OOPS | |
949 | bool "Panic on Oops" | |
a9d9058a | 950 | help |
92aef8fb DH |
951 | Say Y here to enable the kernel to panic when it oopses. This |
952 | has the same effect as setting oops=panic on the kernel command | |
953 | line. | |
a9d9058a | 954 | |
92aef8fb DH |
955 | This feature is useful to ensure that the kernel does not do |
956 | anything erroneous after an oops which could result in data | |
957 | corruption or other issues. | |
958 | ||
959 | Say N if unsure. | |
960 | ||
961 | config PANIC_ON_OOPS_VALUE | |
962 | int | |
963 | range 0 1 | |
964 | default 0 if !PANIC_ON_OOPS | |
965 | default 1 if PANIC_ON_OOPS | |
966 | ||
5800dc3c JB |
967 | config PANIC_TIMEOUT |
968 | int "panic timeout" | |
969 | default 0 | |
970 | help | |
971 | Set the timeout value (in seconds) until a reboot occurs when the | |
972 | the kernel panics. If n = 0, then we wait forever. A timeout | |
973 | value n > 0 will wait n seconds before rebooting, while a timeout | |
974 | value n < 0 will reboot immediately. | |
975 | ||
0610c8a8 DH |
976 | config SCHED_DEBUG |
977 | bool "Collect scheduler debugging info" | |
978 | depends on DEBUG_KERNEL && PROC_FS | |
979 | default y | |
0822ee4a | 980 | help |
0610c8a8 DH |
981 | If you say Y here, the /proc/sched_debug file will be provided |
982 | that can help debug the scheduler. The runtime overhead of this | |
983 | option is minimal. | |
0822ee4a | 984 | |
f6db8347 NR |
985 | config SCHED_INFO |
986 | bool | |
987 | default n | |
988 | ||
0610c8a8 DH |
989 | config SCHEDSTATS |
990 | bool "Collect scheduler statistics" | |
991 | depends on DEBUG_KERNEL && PROC_FS | |
f6db8347 | 992 | select SCHED_INFO |
0610c8a8 DH |
993 | help |
994 | If you say Y here, additional code will be inserted into the | |
995 | scheduler and related routines to collect statistics about | |
996 | scheduler behavior and provide them in /proc/schedstat. These | |
997 | stats may be useful for both tuning and debugging the scheduler | |
998 | If you aren't debugging the scheduler or trying to tune a specific | |
999 | application, you can say N to avoid the very slight overhead | |
1000 | this adds. | |
0822ee4a | 1001 | |
0d9e2632 AT |
1002 | config SCHED_STACK_END_CHECK |
1003 | bool "Detect stack corruption on calls to schedule()" | |
1004 | depends on DEBUG_KERNEL | |
1005 | default n | |
1006 | help | |
1007 | This option checks for a stack overrun on calls to schedule(). | |
1008 | If the stack end location is found to be over written always panic as | |
1009 | the content of the corrupted region can no longer be trusted. | |
1010 | This is to ensure no erroneous behaviour occurs which could result in | |
1011 | data corruption or a sporadic crash at a later stage once the region | |
1012 | is examined. The runtime overhead introduced is minimal. | |
1013 | ||
3c17ad19 JS |
1014 | config DEBUG_TIMEKEEPING |
1015 | bool "Enable extra timekeeping sanity checking" | |
1016 | help | |
1017 | This option will enable additional timekeeping sanity checks | |
1018 | which may be helpful when diagnosing issues where timekeeping | |
1019 | problems are suspected. | |
1020 | ||
1021 | This may include checks in the timekeeping hotpaths, so this | |
1022 | option may have a (very small) performance impact to some | |
1023 | workloads. | |
1024 | ||
1025 | If unsure, say N. | |
1026 | ||
1da177e4 LT |
1027 | config DEBUG_PREEMPT |
1028 | bool "Debug preemptible kernel" | |
01deab98 | 1029 | depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT |
1da177e4 LT |
1030 | default y |
1031 | help | |
1032 | If you say Y here then the kernel will use a debug variant of the | |
1033 | commonly used smp_processor_id() function and will print warnings | |
1034 | if kernel code uses it in a preemption-unsafe way. Also, the kernel | |
1035 | will detect preemption count underflows. | |
1036 | ||
9eade16b DH |
1037 | menu "Lock Debugging (spinlocks, mutexes, etc...)" |
1038 | ||
f07cbebb WL |
1039 | config LOCK_DEBUGGING_SUPPORT |
1040 | bool | |
1041 | depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT | |
1042 | default y | |
1043 | ||
19193bca WL |
1044 | config PROVE_LOCKING |
1045 | bool "Lock debugging: prove locking correctness" | |
1046 | depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT | |
1047 | select LOCKDEP | |
1048 | select DEBUG_SPINLOCK | |
1049 | select DEBUG_MUTEXES | |
1050 | select DEBUG_RT_MUTEXES if RT_MUTEXES | |
1051 | select DEBUG_RWSEMS if RWSEM_SPIN_ON_OWNER | |
1052 | select DEBUG_WW_MUTEX_SLOWPATH | |
1053 | select DEBUG_LOCK_ALLOC | |
1054 | select TRACE_IRQFLAGS | |
1055 | default n | |
1056 | help | |
1057 | This feature enables the kernel to prove that all locking | |
1058 | that occurs in the kernel runtime is mathematically | |
1059 | correct: that under no circumstance could an arbitrary (and | |
1060 | not yet triggered) combination of observed locking | |
1061 | sequences (on an arbitrary number of CPUs, running an | |
1062 | arbitrary number of tasks and interrupt contexts) cause a | |
1063 | deadlock. | |
1064 | ||
1065 | In short, this feature enables the kernel to report locking | |
1066 | related deadlocks before they actually occur. | |
1067 | ||
1068 | The proof does not depend on how hard and complex a | |
1069 | deadlock scenario would be to trigger: how many | |
1070 | participant CPUs, tasks and irq-contexts would be needed | |
1071 | for it to trigger. The proof also does not depend on | |
1072 | timing: if a race and a resulting deadlock is possible | |
1073 | theoretically (no matter how unlikely the race scenario | |
1074 | is), it will be proven so and will immediately be | |
1075 | reported by the kernel (once the event is observed that | |
1076 | makes the deadlock theoretically possible). | |
1077 | ||
1078 | If a deadlock is impossible (i.e. the locking rules, as | |
1079 | observed by the kernel, are mathematically correct), the | |
1080 | kernel reports nothing. | |
1081 | ||
1082 | NOTE: this feature can also be enabled for rwlocks, mutexes | |
1083 | and rwsems - in which case all dependencies between these | |
1084 | different locking variants are observed and mapped too, and | |
1085 | the proof of observed correctness is also maintained for an | |
1086 | arbitrary combination of these separate locking variants. | |
1087 | ||
1088 | For more details, see Documentation/locking/lockdep-design.txt. | |
1089 | ||
1090 | config LOCK_STAT | |
1091 | bool "Lock usage statistics" | |
1092 | depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT | |
1093 | select LOCKDEP | |
1094 | select DEBUG_SPINLOCK | |
1095 | select DEBUG_MUTEXES | |
1096 | select DEBUG_RT_MUTEXES if RT_MUTEXES | |
1097 | select DEBUG_LOCK_ALLOC | |
1098 | default n | |
1099 | help | |
1100 | This feature enables tracking lock contention points | |
1101 | ||
1102 | For more details, see Documentation/locking/lockstat.txt | |
1103 | ||
1104 | This also enables lock events required by "perf lock", | |
1105 | subcommand of perf. | |
1106 | If you want to use "perf lock", you also need to turn on | |
1107 | CONFIG_EVENT_TRACING. | |
1108 | ||
1109 | CONFIG_LOCK_STAT defines "contended" and "acquired" lock events. | |
1110 | (CONFIG_LOCKDEP defines "acquire" and "release" events.) | |
1111 | ||
e7eebaf6 IM |
1112 | config DEBUG_RT_MUTEXES |
1113 | bool "RT Mutex debugging, deadlock detection" | |
e7eebaf6 IM |
1114 | depends on DEBUG_KERNEL && RT_MUTEXES |
1115 | help | |
1116 | This allows rt mutex semantics violations and rt mutex related | |
1117 | deadlocks (lockups) to be detected and reported automatically. | |
1118 | ||
1da177e4 | 1119 | config DEBUG_SPINLOCK |
4d9f34ad | 1120 | bool "Spinlock and rw-lock debugging: basic checks" |
1da177e4 | 1121 | depends on DEBUG_KERNEL |
e335e3eb | 1122 | select UNINLINE_SPIN_UNLOCK |
1da177e4 LT |
1123 | help |
1124 | Say Y here and build SMP to catch missing spinlock initialization | |
1125 | and certain other kinds of spinlock errors commonly made. This is | |
1126 | best used in conjunction with the NMI watchdog so that spinlock | |
1127 | deadlocks are also debuggable. | |
1128 | ||
4d9f34ad IM |
1129 | config DEBUG_MUTEXES |
1130 | bool "Mutex debugging: basic checks" | |
1131 | depends on DEBUG_KERNEL | |
1132 | help | |
1133 | This feature allows mutex semantics violations to be detected and | |
1134 | reported. | |
1135 | ||
23010027 DV |
1136 | config DEBUG_WW_MUTEX_SLOWPATH |
1137 | bool "Wait/wound mutex debugging: Slowpath testing" | |
f07cbebb | 1138 | depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
23010027 DV |
1139 | select DEBUG_LOCK_ALLOC |
1140 | select DEBUG_SPINLOCK | |
1141 | select DEBUG_MUTEXES | |
1142 | help | |
1143 | This feature enables slowpath testing for w/w mutex users by | |
1144 | injecting additional -EDEADLK wound/backoff cases. Together with | |
1145 | the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this | |
1146 | will test all possible w/w mutex interface abuse with the | |
1147 | exception of simply not acquiring all the required locks. | |
4d692373 RC |
1148 | Note that this feature can introduce significant overhead, so |
1149 | it really should not be enabled in a production or distro kernel, | |
1150 | even a debug kernel. If you are a driver writer, enable it. If | |
1151 | you are a distro, do not. | |
23010027 | 1152 | |
5149cbac WL |
1153 | config DEBUG_RWSEMS |
1154 | bool "RW Semaphore debugging: basic checks" | |
1155 | depends on DEBUG_KERNEL && RWSEM_SPIN_ON_OWNER | |
1156 | help | |
1157 | This debugging feature allows mismatched rw semaphore locks and unlocks | |
1158 | to be detected and reported. | |
1159 | ||
4d9f34ad IM |
1160 | config DEBUG_LOCK_ALLOC |
1161 | bool "Lock debugging: detect incorrect freeing of live locks" | |
f07cbebb | 1162 | depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
4d9f34ad IM |
1163 | select DEBUG_SPINLOCK |
1164 | select DEBUG_MUTEXES | |
f5694788 | 1165 | select DEBUG_RT_MUTEXES if RT_MUTEXES |
4d9f34ad IM |
1166 | select LOCKDEP |
1167 | help | |
1168 | This feature will check whether any held lock (spinlock, rwlock, | |
1169 | mutex or rwsem) is incorrectly freed by the kernel, via any of the | |
1170 | memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), | |
1171 | vfree(), etc.), whether a live lock is incorrectly reinitialized via | |
1172 | spin_lock_init()/mutex_init()/etc., or whether there is any lock | |
1173 | held during task exit. | |
1174 | ||
4d9f34ad IM |
1175 | config LOCKDEP |
1176 | bool | |
f07cbebb | 1177 | depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
4d9f34ad | 1178 | select STACKTRACE |
f5a8eb63 | 1179 | select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE && !ARC && !X86 |
4d9f34ad IM |
1180 | select KALLSYMS |
1181 | select KALLSYMS_ALL | |
1182 | ||
395102db DJ |
1183 | config LOCKDEP_SMALL |
1184 | bool | |
1185 | ||
4d9f34ad IM |
1186 | config DEBUG_LOCKDEP |
1187 | bool "Lock dependency engine debugging" | |
517e7aa5 | 1188 | depends on DEBUG_KERNEL && LOCKDEP |
4d9f34ad IM |
1189 | help |
1190 | If you say Y here, the lock dependency engine will do | |
1191 | additional runtime checks to debug itself, at the price | |
1192 | of more runtime overhead. | |
1193 | ||
d902db1e FW |
1194 | config DEBUG_ATOMIC_SLEEP |
1195 | bool "Sleep inside atomic section checking" | |
e8f7c70f | 1196 | select PREEMPT_COUNT |
1da177e4 LT |
1197 | depends on DEBUG_KERNEL |
1198 | help | |
1199 | If you say Y here, various routines which may sleep will become very | |
d902db1e FW |
1200 | noisy if they are called inside atomic sections: when a spinlock is |
1201 | held, inside an rcu read side critical section, inside preempt disabled | |
1202 | sections, inside an interrupt, etc... | |
1da177e4 | 1203 | |
cae2ed9a IM |
1204 | config DEBUG_LOCKING_API_SELFTESTS |
1205 | bool "Locking API boot-time self-tests" | |
1206 | depends on DEBUG_KERNEL | |
1207 | help | |
1208 | Say Y here if you want the kernel to run a short self-test during | |
1209 | bootup. The self-test checks whether common types of locking bugs | |
1210 | are detected by debugging mechanisms or not. (if you disable | |
1211 | lock debugging then those bugs wont be detected of course.) | |
1212 | The following locking APIs are covered: spinlocks, rwlocks, | |
1213 | mutexes and rwsems. | |
1214 | ||
0af3fe1e PM |
1215 | config LOCK_TORTURE_TEST |
1216 | tristate "torture tests for locking" | |
1217 | depends on DEBUG_KERNEL | |
1218 | select TORTURE_TEST | |
1219 | default n | |
1220 | help | |
1221 | This option provides a kernel module that runs torture tests | |
1222 | on kernel locking primitives. The kernel module may be built | |
1223 | after the fact on the running kernel to be tested, if desired. | |
1224 | ||
1225 | Say Y here if you want kernel locking-primitive torture tests | |
1226 | to be built into the kernel. | |
1227 | Say M if you want these torture tests to build as a module. | |
1228 | Say N if you are unsure. | |
1229 | ||
f2a5fec1 CW |
1230 | config WW_MUTEX_SELFTEST |
1231 | tristate "Wait/wound mutex selftests" | |
1232 | help | |
1233 | This option provides a kernel module that runs tests on the | |
1234 | on the struct ww_mutex locking API. | |
1235 | ||
1236 | It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction | |
1237 | with this test harness. | |
1238 | ||
1239 | Say M if you want these self tests to build as a module. | |
1240 | Say N if you are unsure. | |
1241 | ||
9eade16b | 1242 | endmenu # lock debugging |
8637c099 | 1243 | |
9eade16b DH |
1244 | config TRACE_IRQFLAGS |
1245 | bool | |
5ca43f6c | 1246 | help |
9eade16b DH |
1247 | Enables hooks to interrupt enabling and disabling for |
1248 | either tracing or lock debugging. | |
5ca43f6c | 1249 | |
8637c099 | 1250 | config STACKTRACE |
0c38e1fe | 1251 | bool "Stack backtrace support" |
8637c099 | 1252 | depends on STACKTRACE_SUPPORT |
0c38e1fe DJ |
1253 | help |
1254 | This option causes the kernel to create a /proc/pid/stack for | |
1255 | every process, showing its current stack trace. | |
1256 | It is also used by various kernel debugging features that require | |
1257 | stack trace generation. | |
5ca43f6c | 1258 | |
eecabf56 TT |
1259 | config WARN_ALL_UNSEEDED_RANDOM |
1260 | bool "Warn for all uses of unseeded randomness" | |
1261 | default n | |
d06bfd19 JD |
1262 | help |
1263 | Some parts of the kernel contain bugs relating to their use of | |
1264 | cryptographically secure random numbers before it's actually possible | |
1265 | to generate those numbers securely. This setting ensures that these | |
1266 | flaws don't go unnoticed, by enabling a message, should this ever | |
1267 | occur. This will allow people with obscure setups to know when things | |
1268 | are going wrong, so that they might contact developers about fixing | |
1269 | it. | |
1270 | ||
eecabf56 TT |
1271 | Unfortunately, on some models of some architectures getting |
1272 | a fully seeded CRNG is extremely difficult, and so this can | |
1273 | result in dmesg getting spammed for a surprisingly long | |
1274 | time. This is really bad from a security perspective, and | |
1275 | so architecture maintainers really need to do what they can | |
1276 | to get the CRNG seeded sooner after the system is booted. | |
1277 | However, since users can not do anything actionble to | |
1278 | address this, by default the kernel will issue only a single | |
1279 | warning for the first use of unseeded randomness. | |
1280 | ||
1281 | Say Y here if you want to receive warnings for all uses of | |
1282 | unseeded randomness. This will be of use primarily for | |
1283 | those developers interersted in improving the security of | |
1284 | Linux kernels running on their architecture (or | |
1285 | subarchitecture). | |
d06bfd19 | 1286 | |
1da177e4 LT |
1287 | config DEBUG_KOBJECT |
1288 | bool "kobject debugging" | |
1289 | depends on DEBUG_KERNEL | |
1290 | help | |
1291 | If you say Y here, some extra kobject debugging messages will be sent | |
1292 | to the syslog. | |
1293 | ||
c817a67e RK |
1294 | config DEBUG_KOBJECT_RELEASE |
1295 | bool "kobject release debugging" | |
2a999aa0 | 1296 | depends on DEBUG_OBJECTS_TIMERS |
c817a67e RK |
1297 | help |
1298 | kobjects are reference counted objects. This means that their | |
1299 | last reference count put is not predictable, and the kobject can | |
1300 | live on past the point at which a driver decides to drop it's | |
1301 | initial reference to the kobject gained on allocation. An | |
1302 | example of this would be a struct device which has just been | |
1303 | unregistered. | |
1304 | ||
1305 | However, some buggy drivers assume that after such an operation, | |
1306 | the memory backing the kobject can be immediately freed. This | |
1307 | goes completely against the principles of a refcounted object. | |
1308 | ||
1309 | If you say Y here, the kernel will delay the release of kobjects | |
1310 | on the last reference count to improve the visibility of this | |
1311 | kind of kobject release bug. | |
1312 | ||
9b2a60c4 CM |
1313 | config HAVE_DEBUG_BUGVERBOSE |
1314 | bool | |
1315 | ||
1da177e4 | 1316 | config DEBUG_BUGVERBOSE |
6a108a14 | 1317 | bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT |
9b2a60c4 | 1318 | depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE) |
8420e7ef | 1319 | default y |
1da177e4 LT |
1320 | help |
1321 | Say Y here to make BUG() panics output the file name and line number | |
1322 | of the BUG call as well as the EIP and oops trace. This aids | |
1323 | debugging but costs about 70-100K of memory. | |
1324 | ||
199a9afc DJ |
1325 | config DEBUG_LIST |
1326 | bool "Debug linked list manipulation" | |
4520bcb2 | 1327 | depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION |
199a9afc DJ |
1328 | help |
1329 | Enable this to turn on extended checks in the linked-list | |
1330 | walking routines. | |
1331 | ||
1332 | If unsure, say N. | |
1333 | ||
b8cfff68 DS |
1334 | config DEBUG_PI_LIST |
1335 | bool "Debug priority linked list manipulation" | |
1336 | depends on DEBUG_KERNEL | |
1337 | help | |
1338 | Enable this to turn on extended checks in the priority-ordered | |
1339 | linked-list (plist) walking routines. This checks the entire | |
1340 | list multiple times during each manipulation. | |
1341 | ||
1342 | If unsure, say N. | |
1343 | ||
d6ec0842 JA |
1344 | config DEBUG_SG |
1345 | bool "Debug SG table operations" | |
1346 | depends on DEBUG_KERNEL | |
1347 | help | |
1348 | Enable this to turn on checks on scatter-gather tables. This can | |
1349 | help find problems with drivers that do not properly initialize | |
1350 | their sg tables. | |
1351 | ||
1352 | If unsure, say N. | |
1353 | ||
1b2439db AV |
1354 | config DEBUG_NOTIFIERS |
1355 | bool "Debug notifier call chains" | |
1356 | depends on DEBUG_KERNEL | |
1357 | help | |
1358 | Enable this to turn on sanity checking for notifier call chains. | |
1359 | This is most useful for kernel developers to make sure that | |
1360 | modules properly unregister themselves from notifier chains. | |
1361 | This is a relatively cheap check but if you care about maximum | |
1362 | performance, say N. | |
1363 | ||
e0e81739 DH |
1364 | config DEBUG_CREDENTIALS |
1365 | bool "Debug credential management" | |
1366 | depends on DEBUG_KERNEL | |
1367 | help | |
1368 | Enable this to turn on some debug checking for credential | |
1369 | management. The additional code keeps track of the number of | |
1370 | pointers from task_structs to any given cred struct, and checks to | |
1371 | see that this number never exceeds the usage count of the cred | |
1372 | struct. | |
1373 | ||
1374 | Furthermore, if SELinux is enabled, this also checks that the | |
1375 | security pointer in the cred struct is never seen to be invalid. | |
1376 | ||
1377 | If unsure, say N. | |
1378 | ||
43a0a2a7 | 1379 | source "kernel/rcu/Kconfig.debug" |
2f03e3ca | 1380 | |
f303fccb TH |
1381 | config DEBUG_WQ_FORCE_RR_CPU |
1382 | bool "Force round-robin CPU selection for unbound work items" | |
1383 | depends on DEBUG_KERNEL | |
1384 | default n | |
1385 | help | |
1386 | Workqueue used to implicitly guarantee that work items queued | |
1387 | without explicit CPU specified are put on the local CPU. This | |
1388 | guarantee is no longer true and while local CPU is still | |
1389 | preferred work items may be put on foreign CPUs. Kernel | |
1390 | parameter "workqueue.debug_force_rr_cpu" is added to force | |
1391 | round-robin CPU selection to flush out usages which depend on the | |
1392 | now broken guarantee. This config option enables the debug | |
1393 | feature by default. When enabled, memory and cache locality will | |
1394 | be impacted. | |
1395 | ||
870d6656 TH |
1396 | config DEBUG_BLOCK_EXT_DEVT |
1397 | bool "Force extended block device numbers and spread them" | |
1398 | depends on DEBUG_KERNEL | |
1399 | depends on BLOCK | |
759f8ca3 | 1400 | default n |
870d6656 | 1401 | help |
0e11e342 TH |
1402 | BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON |
1403 | SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT | |
1404 | YOU ARE DOING. Distros, please enable this and fix whatever | |
1405 | is broken. | |
1406 | ||
870d6656 TH |
1407 | Conventionally, block device numbers are allocated from |
1408 | predetermined contiguous area. However, extended block area | |
1409 | may introduce non-contiguous block device numbers. This | |
1410 | option forces most block device numbers to be allocated from | |
1411 | the extended space and spreads them to discover kernel or | |
1412 | userland code paths which assume predetermined contiguous | |
1413 | device number allocation. | |
1414 | ||
55dc7db7 TH |
1415 | Note that turning on this debug option shuffles all the |
1416 | device numbers for all IDE and SCSI devices including libata | |
1417 | ones, so root partition specified using device number | |
1418 | directly (via rdev or root=MAJ:MIN) won't work anymore. | |
1419 | Textual device names (root=/dev/sdXn) will continue to work. | |
1420 | ||
870d6656 TH |
1421 | Say N if you are unsure. |
1422 | ||
757c989b TG |
1423 | config CPU_HOTPLUG_STATE_CONTROL |
1424 | bool "Enable CPU hotplug state control" | |
1425 | depends on DEBUG_KERNEL | |
1426 | depends on HOTPLUG_CPU | |
1427 | default n | |
1428 | help | |
1429 | Allows to write steps between "offline" and "online" to the CPUs | |
1430 | sysfs target file so states can be stepped granular. This is a debug | |
1431 | option for now as the hotplug machinery cannot be stopped and | |
1432 | restarted at arbitrary points yet. | |
1433 | ||
1434 | Say N if your are unsure. | |
1435 | ||
8d438288 AM |
1436 | config NOTIFIER_ERROR_INJECTION |
1437 | tristate "Notifier error injection" | |
1438 | depends on DEBUG_KERNEL | |
1439 | select DEBUG_FS | |
1440 | help | |
e41e85cc | 1441 | This option provides the ability to inject artificial errors to |
8d438288 AM |
1442 | specified notifier chain callbacks. It is useful to test the error |
1443 | handling of notifier call chain failures. | |
1444 | ||
1445 | Say N if unsure. | |
1446 | ||
048b9c35 AM |
1447 | config PM_NOTIFIER_ERROR_INJECT |
1448 | tristate "PM notifier error injection module" | |
1449 | depends on PM && NOTIFIER_ERROR_INJECTION | |
1450 | default m if PM_DEBUG | |
1451 | help | |
e41e85cc | 1452 | This option provides the ability to inject artificial errors to |
048b9c35 AM |
1453 | PM notifier chain callbacks. It is controlled through debugfs |
1454 | interface /sys/kernel/debug/notifier-error-inject/pm | |
1455 | ||
1456 | If the notifier call chain should be failed with some events | |
1457 | notified, write the error code to "actions/<notifier event>/error". | |
1458 | ||
1459 | Example: Inject PM suspend error (-12 = -ENOMEM) | |
1460 | ||
1461 | # cd /sys/kernel/debug/notifier-error-inject/pm/ | |
1462 | # echo -12 > actions/PM_SUSPEND_PREPARE/error | |
1463 | # echo mem > /sys/power/state | |
1464 | bash: echo: write error: Cannot allocate memory | |
1465 | ||
1466 | To compile this code as a module, choose M here: the module will | |
1467 | be called pm-notifier-error-inject. | |
1468 | ||
1469 | If unsure, say N. | |
1470 | ||
d526e85f BH |
1471 | config OF_RECONFIG_NOTIFIER_ERROR_INJECT |
1472 | tristate "OF reconfig notifier error injection module" | |
1473 | depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION | |
08dfb4dd | 1474 | help |
e41e85cc | 1475 | This option provides the ability to inject artificial errors to |
d526e85f | 1476 | OF reconfig notifier chain callbacks. It is controlled |
08dfb4dd | 1477 | through debugfs interface under |
d526e85f | 1478 | /sys/kernel/debug/notifier-error-inject/OF-reconfig/ |
08dfb4dd AM |
1479 | |
1480 | If the notifier call chain should be failed with some events | |
1481 | notified, write the error code to "actions/<notifier event>/error". | |
1482 | ||
1483 | To compile this code as a module, choose M here: the module will | |
e12a95f4 | 1484 | be called of-reconfig-notifier-error-inject. |
08dfb4dd AM |
1485 | |
1486 | If unsure, say N. | |
1487 | ||
02fff96a NA |
1488 | config NETDEV_NOTIFIER_ERROR_INJECT |
1489 | tristate "Netdev notifier error injection module" | |
1490 | depends on NET && NOTIFIER_ERROR_INJECTION | |
1491 | help | |
1492 | This option provides the ability to inject artificial errors to | |
1493 | netdevice notifier chain callbacks. It is controlled through debugfs | |
1494 | interface /sys/kernel/debug/notifier-error-inject/netdev | |
1495 | ||
1496 | If the notifier call chain should be failed with some events | |
1497 | notified, write the error code to "actions/<notifier event>/error". | |
1498 | ||
1499 | Example: Inject netdevice mtu change error (-22 = -EINVAL) | |
1500 | ||
1501 | # cd /sys/kernel/debug/notifier-error-inject/netdev | |
1502 | # echo -22 > actions/NETDEV_CHANGEMTU/error | |
1503 | # ip link set eth0 mtu 1024 | |
1504 | RTNETLINK answers: Invalid argument | |
1505 | ||
1506 | To compile this code as a module, choose M here: the module will | |
1507 | be called netdev-notifier-error-inject. | |
1508 | ||
1509 | If unsure, say N. | |
1510 | ||
f1b4bd06 MP |
1511 | config FUNCTION_ERROR_INJECTION |
1512 | def_bool y | |
1513 | depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES | |
1514 | ||
6ff1cb35 | 1515 | config FAULT_INJECTION |
1ab8509a AM |
1516 | bool "Fault-injection framework" |
1517 | depends on DEBUG_KERNEL | |
329409ae AM |
1518 | help |
1519 | Provide fault-injection framework. | |
1520 | For more details, see Documentation/fault-injection/. | |
6ff1cb35 | 1521 | |
8a8b6502 | 1522 | config FAILSLAB |
1ab8509a AM |
1523 | bool "Fault-injection capability for kmalloc" |
1524 | depends on FAULT_INJECTION | |
773ff60e | 1525 | depends on SLAB || SLUB |
8a8b6502 | 1526 | help |
1ab8509a | 1527 | Provide fault-injection capability for kmalloc. |
8a8b6502 | 1528 | |
933e312e AM |
1529 | config FAIL_PAGE_ALLOC |
1530 | bool "Fault-injection capabilitiy for alloc_pages()" | |
1ab8509a | 1531 | depends on FAULT_INJECTION |
933e312e | 1532 | help |
1ab8509a | 1533 | Provide fault-injection capability for alloc_pages(). |
933e312e | 1534 | |
c17bb495 | 1535 | config FAIL_MAKE_REQUEST |
86327d19 | 1536 | bool "Fault-injection capability for disk IO" |
581d4e28 | 1537 | depends on FAULT_INJECTION && BLOCK |
c17bb495 | 1538 | help |
1ab8509a | 1539 | Provide fault-injection capability for disk IO. |
c17bb495 | 1540 | |
581d4e28 | 1541 | config FAIL_IO_TIMEOUT |
f4d01439 | 1542 | bool "Fault-injection capability for faking disk interrupts" |
581d4e28 JA |
1543 | depends on FAULT_INJECTION && BLOCK |
1544 | help | |
1545 | Provide fault-injection capability on end IO handling. This | |
1546 | will make the block layer "forget" an interrupt as configured, | |
1547 | thus exercising the error handling. | |
1548 | ||
1549 | Only works with drivers that use the generic timeout handling, | |
1550 | for others it wont do anything. | |
1551 | ||
ab51fbab DB |
1552 | config FAIL_FUTEX |
1553 | bool "Fault-injection capability for futexes" | |
1554 | select DEBUG_FS | |
1555 | depends on FAULT_INJECTION && FUTEX | |
1556 | help | |
1557 | Provide fault-injection capability for futexes. | |
1558 | ||
f1b4bd06 MP |
1559 | config FAULT_INJECTION_DEBUG_FS |
1560 | bool "Debugfs entries for fault-injection capabilities" | |
1561 | depends on FAULT_INJECTION && SYSFS && DEBUG_FS | |
1562 | help | |
1563 | Enable configuration of fault-injection capabilities via debugfs. | |
1564 | ||
4b1a29a7 MH |
1565 | config FAIL_FUNCTION |
1566 | bool "Fault-injection capability for functions" | |
1567 | depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION | |
1568 | help | |
1569 | Provide function-based fault-injection capability. | |
1570 | This will allow you to override a specific function with a return | |
1571 | with given return value. As a result, function caller will see | |
1572 | an error value and have to handle it. This is useful to test the | |
1573 | error handling in various subsystems. | |
1574 | ||
f1b4bd06 MP |
1575 | config FAIL_MMC_REQUEST |
1576 | bool "Fault-injection capability for MMC IO" | |
1577 | depends on FAULT_INJECTION_DEBUG_FS && MMC | |
6ff1cb35 | 1578 | help |
f1b4bd06 MP |
1579 | Provide fault-injection capability for MMC IO. |
1580 | This will make the mmc core return data errors. This is | |
1581 | useful to test the error handling in the mmc block device | |
1582 | and to test how the mmc host driver handles retries from | |
1583 | the block device. | |
1df49008 AM |
1584 | |
1585 | config FAULT_INJECTION_STACKTRACE_FILTER | |
1586 | bool "stacktrace filter for fault-injection capabilities" | |
1587 | depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT | |
6d690dca | 1588 | depends on !X86_64 |
1df49008 | 1589 | select STACKTRACE |
a687a533 | 1590 | select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND && !ARC && !X86 |
1df49008 AM |
1591 | help |
1592 | Provide stacktrace filter for fault-injection capabilities | |
267c4025 | 1593 | |
9745512c AV |
1594 | config LATENCYTOP |
1595 | bool "Latency measuring infrastructure" | |
625fdcaa RD |
1596 | depends on DEBUG_KERNEL |
1597 | depends on STACKTRACE_SUPPORT | |
1598 | depends on PROC_FS | |
a34a766f | 1599 | select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND && !ARC && !X86 |
9745512c AV |
1600 | select KALLSYMS |
1601 | select KALLSYMS_ALL | |
1602 | select STACKTRACE | |
1603 | select SCHEDSTATS | |
1604 | select SCHED_DEBUG | |
9745512c AV |
1605 | help |
1606 | Enable this option if you want to use the LatencyTOP tool | |
1607 | to find out which userspace is blocking on what kernel operations. | |
1608 | ||
16444a8a ACM |
1609 | source kernel/trace/Kconfig |
1610 | ||
cc3fa840 RD |
1611 | config PROVIDE_OHCI1394_DMA_INIT |
1612 | bool "Remote debugging over FireWire early on boot" | |
1613 | depends on PCI && X86 | |
1614 | help | |
1615 | If you want to debug problems which hang or crash the kernel early | |
1616 | on boot and the crashing machine has a FireWire port, you can use | |
1617 | this feature to remotely access the memory of the crashed machine | |
1618 | over FireWire. This employs remote DMA as part of the OHCI1394 | |
1619 | specification which is now the standard for FireWire controllers. | |
1620 | ||
1621 | With remote DMA, you can monitor the printk buffer remotely using | |
1622 | firescope and access all memory below 4GB using fireproxy from gdb. | |
1623 | Even controlling a kernel debugger is possible using remote DMA. | |
1624 | ||
1625 | Usage: | |
1626 | ||
1627 | If ohci1394_dma=early is used as boot parameter, it will initialize | |
1628 | all OHCI1394 controllers which are found in the PCI config space. | |
1629 | ||
1630 | As all changes to the FireWire bus such as enabling and disabling | |
1631 | devices cause a bus reset and thereby disable remote DMA for all | |
1632 | devices, be sure to have the cable plugged and FireWire enabled on | |
1633 | the debugging host before booting the debug target for debugging. | |
1634 | ||
1635 | This code (~1k) is freed after boot. By then, the firewire stack | |
1636 | in charge of the OHCI-1394 controllers should be used instead. | |
1637 | ||
1638 | See Documentation/debugging-via-ohci1394.txt for more information. | |
1639 | ||
1640 | config DMA_API_DEBUG | |
1641 | bool "Enable debugging of DMA-API usage" | |
f616ab59 | 1642 | select NEED_DMA_MAP_STATE |
cc3fa840 RD |
1643 | help |
1644 | Enable this option to debug the use of the DMA API by device drivers. | |
1645 | With this option you will be able to detect common bugs in device | |
1646 | drivers like double-freeing of DMA mappings or freeing mappings that | |
1647 | were never allocated. | |
1648 | ||
1649 | This also attempts to catch cases where a page owned by DMA is | |
1650 | accessed by the cpu in a way that could cause data corruption. For | |
1651 | example, this enables cow_user_page() to check that the source page is | |
1652 | not undergoing DMA. | |
1653 | ||
1654 | This option causes a performance degradation. Use only if you want to | |
1655 | debug device drivers and dma interactions. | |
1656 | ||
1657 | If unsure, say N. | |
1658 | ||
78c47830 RM |
1659 | config DMA_API_DEBUG_SG |
1660 | bool "Debug DMA scatter-gather usage" | |
1661 | default y | |
1662 | depends on DMA_API_DEBUG | |
1663 | help | |
1664 | Perform extra checking that callers of dma_map_sg() have respected the | |
1665 | appropriate segment length/boundary limits for the given device when | |
1666 | preparing DMA scatterlists. | |
1667 | ||
1668 | This is particularly likely to have been overlooked in cases where the | |
1669 | dma_map_sg() API is used for general bulk mapping of pages rather than | |
1670 | preparing literal scatter-gather descriptors, where there is a risk of | |
1671 | unexpected behaviour from DMA API implementations if the scatterlist | |
1672 | is technically out-of-spec. | |
1673 | ||
1674 | If unsure, say N. | |
1675 | ||
d3deafaa VL |
1676 | menuconfig RUNTIME_TESTING_MENU |
1677 | bool "Runtime Testing" | |
908009e8 | 1678 | def_bool y |
d3deafaa VL |
1679 | |
1680 | if RUNTIME_TESTING_MENU | |
881c5149 DH |
1681 | |
1682 | config LKDTM | |
1683 | tristate "Linux Kernel Dump Test Tool Module" | |
1684 | depends on DEBUG_FS | |
1685 | depends on BLOCK | |
1686 | default n | |
1687 | help | |
1688 | This module enables testing of the different dumping mechanisms by | |
1689 | inducing system failures at predefined crash points. | |
1690 | If you don't need it: say N | |
1691 | Choose M here to compile this code as a module. The module will be | |
1692 | called lkdtm. | |
1693 | ||
1694 | Documentation on how to use the module can be found in | |
1695 | Documentation/fault-injection/provoke-crashes.txt | |
1696 | ||
1697 | config TEST_LIST_SORT | |
e327fd7c GU |
1698 | tristate "Linked list sorting test" |
1699 | depends on DEBUG_KERNEL || m | |
881c5149 DH |
1700 | help |
1701 | Enable this to turn on 'list_sort()' function test. This test is | |
e327fd7c GU |
1702 | executed only once during system boot (so affects only boot time), |
1703 | or at module load time. | |
881c5149 DH |
1704 | |
1705 | If unsure, say N. | |
1706 | ||
c5adae95 | 1707 | config TEST_SORT |
5c4e6798 GU |
1708 | tristate "Array-based sort test" |
1709 | depends on DEBUG_KERNEL || m | |
c5adae95 | 1710 | help |
5c4e6798 GU |
1711 | This option enables the self-test function of 'sort()' at boot, |
1712 | or at module load time. | |
c5adae95 KF |
1713 | |
1714 | If unsure, say N. | |
1715 | ||
881c5149 DH |
1716 | config KPROBES_SANITY_TEST |
1717 | bool "Kprobes sanity tests" | |
1718 | depends on DEBUG_KERNEL | |
1719 | depends on KPROBES | |
1720 | default n | |
1721 | help | |
1722 | This option provides for testing basic kprobes functionality on | |
1723 | boot. A sample kprobe, jprobe and kretprobe are inserted and | |
1724 | verified for functionality. | |
1725 | ||
1726 | Say N if you are unsure. | |
1727 | ||
1728 | config BACKTRACE_SELF_TEST | |
1729 | tristate "Self test for the backtrace code" | |
1730 | depends on DEBUG_KERNEL | |
1731 | default n | |
1732 | help | |
1733 | This option provides a kernel module that can be used to test | |
1734 | the kernel stack backtrace code. This option is not useful | |
1735 | for distributions or general kernels, but only for kernel | |
1736 | developers working on architecture code. | |
1737 | ||
1738 | Note that if you want to also test saved backtraces, you will | |
1739 | have to enable STACKTRACE as well. | |
1740 | ||
1741 | Say N if you are unsure. | |
1742 | ||
910a742d ML |
1743 | config RBTREE_TEST |
1744 | tristate "Red-Black tree test" | |
7c993e11 | 1745 | depends on DEBUG_KERNEL |
910a742d ML |
1746 | help |
1747 | A benchmark measuring the performance of the rbtree library. | |
1748 | Also includes rbtree invariant checks. | |
1749 | ||
fff3fd8a ML |
1750 | config INTERVAL_TREE_TEST |
1751 | tristate "Interval tree test" | |
0f789b67 | 1752 | depends on DEBUG_KERNEL |
a88cc108 | 1753 | select INTERVAL_TREE |
fff3fd8a ML |
1754 | help |
1755 | A benchmark measuring the performance of the interval tree library | |
1756 | ||
623fd807 GT |
1757 | config PERCPU_TEST |
1758 | tristate "Per cpu operations test" | |
1759 | depends on m && DEBUG_KERNEL | |
1760 | help | |
1761 | Enable this option to build test module which validates per-cpu | |
1762 | operations. | |
1763 | ||
1764 | If unsure, say N. | |
1765 | ||
881c5149 | 1766 | config ATOMIC64_SELFTEST |
55ded955 | 1767 | tristate "Perform an atomic64_t self-test" |
881c5149 | 1768 | help |
55ded955 GU |
1769 | Enable this option to test the atomic64_t functions at boot or |
1770 | at module load time. | |
881c5149 DH |
1771 | |
1772 | If unsure, say N. | |
1773 | ||
1774 | config ASYNC_RAID6_TEST | |
1775 | tristate "Self test for hardware accelerated raid6 recovery" | |
1776 | depends on ASYNC_RAID6_RECOV | |
1777 | select ASYNC_MEMCPY | |
1778 | ---help--- | |
1779 | This is a one-shot self test that permutes through the | |
1780 | recovery of all the possible two disk failure scenarios for a | |
1781 | N-disk array. Recovery is performed with the asynchronous | |
1782 | raid6 recovery routines, and will optionally use an offload | |
1783 | engine if one is available. | |
1784 | ||
1785 | If unsure, say N. | |
1786 | ||
64d1d77a AS |
1787 | config TEST_HEXDUMP |
1788 | tristate "Test functions located in the hexdump module at runtime" | |
1789 | ||
881c5149 DH |
1790 | config TEST_STRING_HELPERS |
1791 | tristate "Test functions located in the string_helpers module at runtime" | |
1792 | ||
1793 | config TEST_KSTRTOX | |
1794 | tristate "Test kstrto*() family of functions at runtime" | |
1795 | ||
707cc728 RV |
1796 | config TEST_PRINTF |
1797 | tristate "Test printf() family of functions at runtime" | |
1798 | ||
5fd003f5 DD |
1799 | config TEST_BITMAP |
1800 | tristate "Test bitmap_*() family of functions at runtime" | |
1801 | default n | |
1802 | help | |
1803 | Enable this option to test the bitmap functions at boot. | |
1804 | ||
1805 | If unsure, say N. | |
1806 | ||
cfaff0e5 AS |
1807 | config TEST_UUID |
1808 | tristate "Test functions located in the uuid module at runtime" | |
1809 | ||
455a35a6 RV |
1810 | config TEST_OVERFLOW |
1811 | tristate "Test check_*_overflow() functions at runtime" | |
1812 | ||
7e1e7763 | 1813 | config TEST_RHASHTABLE |
9d6dbe1b | 1814 | tristate "Perform selftest on resizable hash table" |
7e1e7763 TG |
1815 | default n |
1816 | help | |
1817 | Enable this option to test the rhashtable functions at boot. | |
1818 | ||
1819 | If unsure, say N. | |
1820 | ||
468a9428 GS |
1821 | config TEST_HASH |
1822 | tristate "Perform selftest on hash functions" | |
1823 | default n | |
1824 | help | |
2c956a60 JD |
1825 | Enable this option to test the kernel's integer (<linux/hash.h>), |
1826 | string (<linux/stringhash.h>), and siphash (<linux/siphash.h>) | |
1827 | hash functions on boot (or module load). | |
468a9428 GS |
1828 | |
1829 | This is intended to help people writing architecture-specific | |
1830 | optimized versions. If unsure, say N. | |
1831 | ||
44091d29 JP |
1832 | config TEST_PARMAN |
1833 | tristate "Perform selftest on priority array manager" | |
1834 | default n | |
1835 | depends on PARMAN | |
1836 | help | |
1837 | Enable this option to test priority array manager on boot | |
1838 | (or module load). | |
1839 | ||
1840 | If unsure, say N. | |
1841 | ||
8a6f0b47 | 1842 | config TEST_LKM |
93e9ef83 KC |
1843 | tristate "Test module loading with 'hello world' module" |
1844 | default n | |
1845 | depends on m | |
1846 | help | |
1847 | This builds the "test_module" module that emits "Hello, world" | |
1848 | on printk when loaded. It is designed to be used for basic | |
1849 | evaluation of the module loading subsystem (for example when | |
1850 | validating module verification). It lacks any extra dependencies, | |
1851 | and will not normally be loaded by the system unless explicitly | |
1852 | requested by name. | |
1853 | ||
1854 | If unsure, say N. | |
1855 | ||
3e2a4c18 KC |
1856 | config TEST_USER_COPY |
1857 | tristate "Test user/kernel boundary protections" | |
1858 | default n | |
1859 | depends on m | |
1860 | help | |
1861 | This builds the "test_user_copy" module that runs sanity checks | |
1862 | on the copy_to/from_user infrastructure, making sure basic | |
1863 | user/kernel boundary testing is working. If it fails to load, | |
1864 | a regression has been detected in the user/kernel memory boundary | |
1865 | protections. | |
1866 | ||
1867 | If unsure, say N. | |
1868 | ||
64a8946b AS |
1869 | config TEST_BPF |
1870 | tristate "Test BPF filter functionality" | |
1871 | default n | |
98920ba6 | 1872 | depends on m && NET |
64a8946b AS |
1873 | help |
1874 | This builds the "test_bpf" module that runs various test vectors | |
1875 | against the BPF interpreter or BPF JIT compiler depending on the | |
1876 | current setting. This is in particular useful for BPF JIT compiler | |
1877 | development, but also to run regression tests against changes in | |
3c731eba AS |
1878 | the interpreter code. It also enables test stubs for eBPF maps and |
1879 | verifier used by user space verifier testsuite. | |
64a8946b AS |
1880 | |
1881 | If unsure, say N. | |
1882 | ||
dceeb3e7 | 1883 | config FIND_BIT_BENCHMARK |
4441fca0 YN |
1884 | tristate "Test find_bit functions" |
1885 | default n | |
1886 | help | |
1887 | This builds the "test_find_bit" module that measure find_*_bit() | |
1888 | functions performance. | |
1889 | ||
1890 | If unsure, say N. | |
1891 | ||
0a8adf58 KC |
1892 | config TEST_FIRMWARE |
1893 | tristate "Test firmware loading via userspace interface" | |
1894 | default n | |
1895 | depends on FW_LOADER | |
1896 | help | |
1897 | This builds the "test_firmware" module that creates a userspace | |
1898 | interface for testing firmware loading. This can be used to | |
1899 | control the triggering of firmware loading without needing an | |
1900 | actual firmware-using device. The contents can be rechecked by | |
1901 | userspace. | |
1902 | ||
1903 | If unsure, say N. | |
1904 | ||
9308f2f9 LR |
1905 | config TEST_SYSCTL |
1906 | tristate "sysctl test driver" | |
1907 | default n | |
1908 | depends on PROC_SYSCTL | |
1909 | help | |
1910 | This builds the "test_sysctl" module. This driver enables to test the | |
1911 | proc sysctl interfaces available to drivers safely without affecting | |
1912 | production knobs which might alter system functionality. | |
1913 | ||
1914 | If unsure, say N. | |
1915 | ||
e704f93a DR |
1916 | config TEST_UDELAY |
1917 | tristate "udelay test driver" | |
1918 | default n | |
1919 | help | |
1920 | This builds the "udelay_test" module that helps to make sure | |
1921 | that udelay() is working properly. | |
1922 | ||
1923 | If unsure, say N. | |
1924 | ||
2bf9e0ab IM |
1925 | config TEST_STATIC_KEYS |
1926 | tristate "Test static keys" | |
579e1acb JB |
1927 | default n |
1928 | depends on m | |
1929 | help | |
2bf9e0ab | 1930 | Test the static key interfaces. |
579e1acb JB |
1931 | |
1932 | If unsure, say N. | |
1933 | ||
d9c6a72d LR |
1934 | config TEST_KMOD |
1935 | tristate "kmod stress tester" | |
1936 | default n | |
1937 | depends on m | |
1938 | depends on BLOCK && (64BIT || LBDAF) # for XFS, BTRFS | |
1939 | depends on NETDEVICES && NET_CORE && INET # for TUN | |
1940 | select TEST_LKM | |
1941 | select XFS_FS | |
1942 | select TUN | |
1943 | select BTRFS_FS | |
1944 | help | |
1945 | Test the kernel's module loading mechanism: kmod. kmod implements | |
1946 | support to load modules using the Linux kernel's usermode helper. | |
1947 | This test provides a series of tests against kmod. | |
1948 | ||
1949 | Although technically you can either build test_kmod as a module or | |
1950 | into the kernel we disallow building it into the kernel since | |
1951 | it stress tests request_module() and this will very likely cause | |
1952 | some issues by taking over precious threads available from other | |
1953 | module load requests, ultimately this could be fatal. | |
1954 | ||
1955 | To run tests run: | |
1956 | ||
1957 | tools/testing/selftests/kmod/kmod.sh --help | |
1958 | ||
1959 | If unsure, say N. | |
1960 | ||
e4dace36 FF |
1961 | config TEST_DEBUG_VIRTUAL |
1962 | tristate "Test CONFIG_DEBUG_VIRTUAL feature" | |
1963 | depends on DEBUG_VIRTUAL | |
1964 | help | |
1965 | Test the kernel's ability to detect incorrect calls to | |
1966 | virt_to_phys() done against the non-linear part of the | |
1967 | kernel's virtual address map. | |
1968 | ||
1969 | If unsure, say N. | |
1970 | ||
d3deafaa | 1971 | endif # RUNTIME_TESTING_MENU |
cc3fa840 RD |
1972 | |
1973 | config MEMTEST | |
1974 | bool "Memtest" | |
1975 | depends on HAVE_MEMBLOCK | |
1976 | ---help--- | |
1977 | This option adds a kernel parameter 'memtest', which allows memtest | |
1978 | to be set. | |
1979 | memtest=0, mean disabled; -- default | |
1980 | memtest=1, mean do 1 test pattern; | |
1981 | ... | |
1982 | memtest=17, mean do 17 test patterns. | |
1983 | If you are unsure how to answer this question, answer N. | |
1984 | ||
1985 | config BUG_ON_DATA_CORRUPTION | |
1986 | bool "Trigger a BUG when data corruption is detected" | |
1987 | select DEBUG_LIST | |
1988 | help | |
1989 | Select this option if the kernel should BUG when it encounters | |
1990 | data corruption in kernel memory structures when they get checked | |
1991 | for validity. | |
1992 | ||
1993 | If unsure, say N. | |
e4dace36 | 1994 | |
267c4025 | 1995 | source "samples/Kconfig" |
dc7d5527 JW |
1996 | |
1997 | source "lib/Kconfig.kgdb" | |
0a4af3b0 | 1998 | |
c6d30853 AR |
1999 | source "lib/Kconfig.ubsan" |
2000 | ||
21266be9 DW |
2001 | config ARCH_HAS_DEVMEM_IS_ALLOWED |
2002 | bool | |
2003 | ||
2004 | config STRICT_DEVMEM | |
2005 | bool "Filter access to /dev/mem" | |
6b2a65c7 | 2006 | depends on MMU && DEVMEM |
21266be9 | 2007 | depends on ARCH_HAS_DEVMEM_IS_ALLOWED |
a687a533 | 2008 | default y if PPC || X86 || ARM64 |
21266be9 DW |
2009 | ---help--- |
2010 | If this option is disabled, you allow userspace (root) access to all | |
2011 | of memory, including kernel and userspace memory. Accidental | |
2012 | access to this is obviously disastrous, but specific access can | |
2013 | be used by people debugging the kernel. Note that with PAT support | |
2014 | enabled, even in this case there are restrictions on /dev/mem | |
2015 | use due to the cache aliasing requirements. | |
2016 | ||
90a545e9 DW |
2017 | If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem |
2018 | file only allows userspace access to PCI space and the BIOS code and | |
2019 | data regions. This is sufficient for dosemu and X and all common | |
2020 | users of /dev/mem. | |
2021 | ||
2022 | If in doubt, say Y. | |
2023 | ||
2024 | config IO_STRICT_DEVMEM | |
2025 | bool "Filter I/O access to /dev/mem" | |
2026 | depends on STRICT_DEVMEM | |
90a545e9 DW |
2027 | ---help--- |
2028 | If this option is disabled, you allow userspace (root) access to all | |
2029 | io-memory regardless of whether a driver is actively using that | |
2030 | range. Accidental access to this is obviously disastrous, but | |
2031 | specific access can be used by people debugging kernel drivers. | |
2032 | ||
21266be9 | 2033 | If this option is switched on, the /dev/mem file only allows |
90a545e9 DW |
2034 | userspace access to *idle* io-memory ranges (see /proc/iomem) This |
2035 | may break traditional users of /dev/mem (dosemu, legacy X, etc...) | |
2036 | if the driver using a given range cannot be disabled. | |
21266be9 DW |
2037 | |
2038 | If in doubt, say Y. | |
06ec64b8 CH |
2039 | |
2040 | source "arch/$(SRCARCH)/Kconfig.debug" | |
2041 | ||
2042 | endmenu # Kernel hacking |