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