Blame view
lib/Kconfig.debug
85.7 KB
ec8f24b7f treewide: Add SPD... |
1 |
# SPDX-License-Identifier: GPL-2.0-only |
06ec64b84 Kconfig: consolid... |
2 |
menu "Kernel hacking" |
604ff0dce kconfig: consolid... |
3 |
menu "printk and dmesg options" |
1da177e4c Linux-2.6.12-rc2 |
4 5 6 |
config PRINTK_TIME bool "Show timing information on printks" |
d3b8b6e5f [PATCH] kconfig: ... |
7 |
depends on PRINTK |
1da177e4c Linux-2.6.12-rc2 |
8 |
help |
649e6ee33 printk() - restor... |
9 10 11 12 13 14 15 16 17 |
Selecting this option causes time stamps of the printk() messages to be added to the output of the syslog() system call and at the console. The timestamp is always recorded internally, and exported to /dev/kmsg. This flag just specifies if the timestamp should be included, not that the timestamp is recorded. The behavior is also controlled by the kernel command line |
8c27ceff3 docs: fix locatio... |
18 |
parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst |
1da177e4c Linux-2.6.12-rc2 |
19 |
|
15ff2069c printk: Add calle... |
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
config PRINTK_CALLER bool "Show caller information on printks" depends on PRINTK help Selecting this option causes printk() to add a caller "thread id" (if in task context) or a caller "processor id" (if not in task context) to every message. This option is intended for environments where multiple threads concurrently call printk() for many times, for it is difficult to interpret without knowing where these lines (or sometimes individual line which was divided into multiple lines due to race) came from. Since toggling after boot makes the code racy, currently there is no option to enable/disable at the kernel command line parameter or sysfs interface. |
22f4e66df dump_stack: add v... |
36 37 38 39 40 41 42 43 44 45 |
config STACKTRACE_BUILD_ID bool "Show build ID information in stacktraces" depends on PRINTK help Selecting this option adds build ID information for symbols in stacktraces printed with the printk format '%p[SR]b'. This option is intended for distros where debuginfo is not easily accessible but can be downloaded given the build ID of the vmlinux or kernel module where the function is located. |
a8cfdc68f printk: add Kconf... |
46 47 48 49 50 51 52 53 54 55 |
config CONSOLE_LOGLEVEL_DEFAULT int "Default console loglevel (1-15)" range 1 15 default "7" help Default loglevel to determine what will be printed on the console. Setting a default here is equivalent to passing in loglevel=<x> in the kernel bootargs. loglevel=<x> continues to override whatever value is specified here as well. |
50f4d9bda printk: fix typo ... |
56 |
Note: This does not affect the log level of un-prefixed printk() |
a8cfdc68f printk: add Kconf... |
57 58 |
usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT option. |
22eceb8bf printk: Make CONS... |
59 60 61 62 63 64 65 66 67 68 |
config CONSOLE_LOGLEVEL_QUIET int "quiet console loglevel (1-15)" range 1 15 default "4" help loglevel to use when "quiet" is passed on the kernel commandline. When "quiet" is passed on the kernel commandline this loglevel will be used as the loglevel. IOW passing "quiet" will be the equivalent of passing "loglevel=<CONSOLE_LOGLEVEL_QUIET>" |
42a9dc0b3 printk: rename DE... |
69 |
config MESSAGE_LOGLEVEL_DEFAULT |
5af5bcb8d printk: allow set... |
70 71 72 73 74 75 76 77 78 |
int "Default message log level (1-7)" range 1 7 default "4" help Default log level for printk statements with no specified priority. This was hard-coded to KERN_WARNING since at least 2.6.10 but folks that are auditing their logs closely may want to set it to a lower priority. |
a8cfdc68f printk: add Kconf... |
79 80 81 |
Note: This does not affect what message level gets printed on the console by default. To change that, use loglevel=<x> in the kernel bootargs, or pick a different CONSOLE_LOGLEVEL_DEFAULT configuration value. |
604ff0dce kconfig: consolid... |
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 |
config BOOT_PRINTK_DELAY bool "Delay each boot printk message by N milliseconds" depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY help This build option allows you to read kernel boot messages by inserting a short delay after each one. The delay is specified in milliseconds on the kernel command line, using "boot_delay=N". It is likely that you would also need to use "lpj=M" to preset the "loops per jiffie" value. See a previous boot log for the "lpj" value to use for your system, and then set "lpj=M" before setting "boot_delay=N". NOTE: Using this option may adversely affect SMP systems. I.e., processors other than the first one may not boot up. BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect what it believes to be lockup conditions. config DYNAMIC_DEBUG bool "Enable dynamic printk() support" default n depends on PRINTK |
239a5791f dynamic_debug: al... |
104 |
depends on (DEBUG_FS || PROC_FS) |
ceabef7dd dynamic_debug: ad... |
105 |
select DYNAMIC_DEBUG_CORE |
604ff0dce kconfig: consolid... |
106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 |
help Compiles debug level messages into the kernel, which would not otherwise be available at runtime. These messages can then be enabled/disabled based on various levels of scope - per source file, function, module, format string, and line number. This mechanism implicitly compiles in all pr_debug() and dev_dbg() calls, which enlarges the kernel text size by about 2%. If a source file is compiled with DEBUG flag set, any pr_debug() calls in it are enabled by default, but can be disabled at runtime as below. Note that DEBUG flag is turned on by many CONFIG_*DEBUG* options. Usage: Dynamic debugging is controlled via the 'dynamic_debug/control' file, |
239a5791f dynamic_debug: al... |
123 124 125 |
which is contained in the 'debugfs' filesystem or procfs. Thus, the debugfs or procfs filesystem must first be mounted before making use of this feature. |
604ff0dce kconfig: consolid... |
126 127 128 129 130 131 132 133 134 135 |
We refer the control file as: <debugfs>/dynamic_debug/control. This file contains a list of the debug statements that can be enabled. The format for each line of the file is: filename:lineno [module]function flags format filename : source file of the debug statement lineno : line number of the debug statement module : module that contains the debug statement function : function that contains the debug statement |
68d4b3dfc lib/: fix Kconfig... |
136 137 |
flags : '=p' means the line is turned 'on' for printing format : the format used for the debug statement |
604ff0dce kconfig: consolid... |
138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 |
From a live system: nullarbor:~ # cat <debugfs>/dynamic_debug/control # filename:lineno [module]function flags format fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012" fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012" fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012" Example usage: // enable the message at line 1603 of file svcsock.c nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' > <debugfs>/dynamic_debug/control // enable all the messages in file svcsock.c nullarbor:~ # echo -n 'file svcsock.c +p' > <debugfs>/dynamic_debug/control // enable all the messages in the NFS server module nullarbor:~ # echo -n 'module nfsd +p' > <debugfs>/dynamic_debug/control // enable all 12 messages in the function svc_process() nullarbor:~ # echo -n 'func svc_process +p' > <debugfs>/dynamic_debug/control // disable all 12 messages in the function svc_process() nullarbor:~ # echo -n 'func svc_process -p' > <debugfs>/dynamic_debug/control |
f8998c226 lib/Kconfig.debug... |
168 169 |
See Documentation/admin-guide/dynamic-debug-howto.rst for additional information. |
604ff0dce kconfig: consolid... |
170 |
|
ceabef7dd dynamic_debug: ad... |
171 172 173 174 175 176 177 178 179 180 |
config DYNAMIC_DEBUG_CORE bool "Enable core function of dynamic debug support" depends on PRINTK depends on (DEBUG_FS || PROC_FS) help Enable core functional support of dynamic debug. It is useful when you want to tie dynamic debug to your kernel modules with DYNAMIC_DEBUG_MODULE defined for each of them, especially for the case of embedded system where the kernel image size is sensitive for people. |
57f5677e5 printf: add suppo... |
181 182 183 184 185 186 187 188 |
config SYMBOLIC_ERRNAME bool "Support symbolic error names in printf" default y if PRINTK help If you say Y here, the kernel's printf implementation will be able to print symbolic error names such as ENOSPC instead of the number 28. It makes the kernel image slightly larger (about 3KB), but can make the kernel logs easier to read. |
2b05bb75d kernel-hacking: m... |
189 190 191 192 193 194 195 196 |
config DEBUG_BUGVERBOSE bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE) default y help Say Y here to make BUG() panics output the file name and line number of the BUG call as well as the EIP and oops trace. This aids debugging but costs about 70-100K of memory. |
604ff0dce kconfig: consolid... |
197 |
endmenu # "printk and dmesg options" |
6dfc06651 consolidate compi... |
198 199 200 201 |
menu "Compile-time checks and compiler options" config DEBUG_INFO bool "Compile the kernel with debug info" |
12b13835a kbuild: don't ena... |
202 |
depends on DEBUG_KERNEL && !COMPILE_TEST |
6dfc06651 consolidate compi... |
203 |
help |
68d4b3dfc lib/: fix Kconfig... |
204 |
If you say Y here the resulting kernel image will include |
6dfc06651 consolidate compi... |
205 206 207 208 209 210 211 |
debugging info resulting in a larger kernel image. This adds debug symbols to the kernel and modules (gcc -g), and is needed if you intend to use kernel crashdump or binary object tools like crash, kgdb, LKCD, gdb, etc on the kernel. Say Y here only if you plan to debug the kernel. If unsure, say N. |
695afd3d7 kbuild: Simplify ... |
212 |
if DEBUG_INFO |
6dfc06651 consolidate compi... |
213 214 |
config DEBUG_INFO_REDUCED bool "Reduce debugging information" |
6dfc06651 consolidate compi... |
215 216 217 218 219 220 221 222 223 |
help If you say Y here gcc is instructed to generate less debugging information for structure types. This means that tools that need full debugging information (like kgdb or systemtap) won't be happy. But if you merely need debugging information to resolve line numbers there is no loss. Advantage is that build directory object sizes shrink dramatically over a full DEBUG_INFO build and compile times are reduced too. Only works with newer gcc versions. |
10e68b02c Makefile: support... |
224 225 |
config DEBUG_INFO_COMPRESSED bool "Compressed debugging information" |
10e68b02c Makefile: support... |
226 |
depends on $(cc-option,-gz=zlib) |
10e68b02c Makefile: support... |
227 228 229 230 231 232 233 234 235 236 237 |
depends on $(ld-option,--compress-debug-sections=zlib) help Compress the debug information using zlib. Requires GCC 5.0+ or Clang 5.0+, binutils 2.26+, and zlib. Users of dpkg-deb via scripts/package/builddeb may find an increase in size of their debug .deb packages with this config set, due to the debug info being compressed with zlib, then the object files being recompressed with a different compression scheme. But this is still preferable to setting $KDEB_COMPRESS to "none" which would be even larger. |
866ced950 kbuild: Support s... |
238 239 |
config DEBUG_INFO_SPLIT bool "Produce split debuginfo in .dwo files" |
9d9374440 kbuild: move -gsp... |
240 |
depends on $(cc-option,-gsplit-dwarf) |
866ced950 kbuild: Support s... |
241 242 243 244 245 246 247 248 249 250 251 |
help Generate debug info into separate .dwo files. This significantly reduces the build directory size for builds with DEBUG_INFO, because it stores the information only once on disk in .dwo files instead of multiple times in object files and executables. In addition the debug information is also compressed. Requires recent gcc (4.7+) and recent gdb/binutils. Any tool that packages or reads debug information would need to know about the .dwo files and include them. Incompatible with older versions of ccache. |
a66049e2c Kbuild: make DWAR... |
252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 |
choice prompt "DWARF version" help Which version of DWARF debug info to emit. config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT bool "Rely on the toolchain's implicit default DWARF version" help The implicit default version of DWARF debug info produced by a toolchain changes over time. This can break consumers of the debug info that haven't upgraded to support newer revisions, and prevent testing newer versions, but those should be less common scenarios. If unsure, say Y. |
bfaf2dd35 Kbuild: Add a opt... |
268 |
config DEBUG_INFO_DWARF4 |
a66049e2c Kbuild: make DWAR... |
269 |
bool "Generate DWARF Version 4 debuginfo" |
bfaf2dd35 Kbuild: Add a opt... |
270 |
help |
a66049e2c Kbuild: make DWAR... |
271 272 273 274 275 |
Generate DWARF v4 debug info. This requires gcc 4.5+ and gdb 7.0+. If you have consumers of DWARF debug info that are not ready for newer revisions of DWARF, you may wish to choose this or have your config select this. |
98cd6f521 Kconfig: allow ex... |
276 277 |
config DEBUG_INFO_DWARF5 bool "Generate DWARF Version 5 debuginfo" |
c0a5c81ca Kconfig.debug: dr... |
278 |
depends on !CC_IS_CLANG || (CC_IS_CLANG && (AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502))) |
98cd6f521 Kconfig: allow ex... |
279 |
depends on !DEBUG_INFO_BTF |
bfaf2dd35 Kbuild: Add a opt... |
280 |
help |
98cd6f521 Kconfig: allow ex... |
281 282 283 284 285 286 287 288 289 290 291 |
Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc 5.0+ accepts the -gdwarf-5 flag but only had partial support for some draft features until 7.0), and gdb 8.0+. Changes to the structure of debug info in Version 5 allow for around 15-18% savings in resulting image and debug info section sizes as compared to DWARF Version 4. DWARF Version 5 standardizes previous extensions such as accelerators for symbol indexing and the format for fission (.dwo/.dwp) files. Users may not want to select this config if they rely on tooling that has not yet been updated to support DWARF Version 5. |
a66049e2c Kbuild: make DWAR... |
292 |
endchoice # "DWARF version" |
bfaf2dd35 Kbuild: Add a opt... |
293 |
|
e83b9f554 kbuild: add abili... |
294 295 |
config DEBUG_INFO_BTF bool "Generate BTF typeinfo" |
7d32e6931 kbuild, btf: Fix ... |
296 297 |
depends on !DEBUG_INFO_SPLIT && !DEBUG_INFO_REDUCED depends on !GCC_PLUGIN_RANDSTRUCT || COMPILE_TEST |
e83b9f554 kbuild: add abili... |
298 299 300 301 |
help Generate deduplicated BTF type information from DWARF debug info. Turning this on expects presence of pahole tool, which will convert DWARF type info into equivalent deduplicated BTF type info. |
5f9ae91f7 kbuild: Build ker... |
302 303 304 305 306 307 308 309 |
config PAHOLE_HAS_SPLIT_BTF def_bool $(success, test `$(PAHOLE) --version | sed -E 's/v([0-9]+)\.([0-9]+)/\1\2/'` -ge "119") config DEBUG_INFO_BTF_MODULES def_bool y depends on DEBUG_INFO_BTF && MODULES && PAHOLE_HAS_SPLIT_BTF help Generate compact split BTF type information for kernel modules. |
3ee7b3fa2 scripts/gdb: add ... |
310 311 |
config GDB_SCRIPTS bool "Provide GDB scripts for kernel debugging" |
3ee7b3fa2 scripts/gdb: add ... |
312 313 314 315 316 |
help This creates the required links to GDB helper scripts in the build directory. If you load vmlinux into gdb, the helper scripts will be automatically imported by gdb as well, and additional functions are available to analyze a Linux kernel |
700199b0c Kconfig: lib/Kcon... |
317 318 |
instance. See Documentation/dev-tools/gdb-kernel-debugging.rst for further details. |
3ee7b3fa2 scripts/gdb: add ... |
319 |
|
695afd3d7 kbuild: Simplify ... |
320 |
endif # DEBUG_INFO |
35bb5b1e0 Add option to ena... |
321 |
config FRAME_WARN |
a83e4ca26 kbuild: remove cc... |
322 |
int "Warn for stack frames larger than" |
35bb5b1e0 Add option to ena... |
323 |
range 0 8192 |
0e07f663c latent_entropy: r... |
324 |
default 2048 if GCC_PLUGIN_LATENT_ENTROPY |
867050247 xtensa: increase ... |
325 |
default 1536 if (!64BIT && (PARISC || XTENSA)) |
432654df9 parisc: Fix too l... |
326 |
default 1024 if (!64BIT && !PARISC) |
35bb5b1e0 Add option to ena... |
327 328 329 330 331 |
default 2048 if 64BIT help Tell gcc to warn at build time for stack frames larger than this. Setting this too low will cause a lot of warnings. Setting it to 0 disables the warning. |
35bb5b1e0 Add option to ena... |
332 |
|
99657c785 kernel hacking: m... |
333 334 335 336 337 338 339 |
config STRIP_ASM_SYMS bool "Strip assembler-generated symbols during link" default n help Strip internal assembler-generated symbols during a link (symbols that look like '.Lxxx') so they don't pollute the output of get_wchan() and suchlike. |
1873e870f debug: Add CONFIG... |
340 |
config READABLE_ASM |
68d4b3dfc lib/: fix Kconfig... |
341 342 |
bool "Generate readable assembler code" depends on DEBUG_KERNEL |
7d73c3e9c Makefile: remove ... |
343 |
depends on CC_IS_GCC |
bf4735a46 [PATCH] Kconfig r... |
344 |
help |
68d4b3dfc lib/: fix Kconfig... |
345 346 347 348 |
Disable some compiler optimizations that tend to generate human unreadable assembler output. This may make the kernel slightly slower, but it helps to keep kernel developers who have to stare a lot at assembler listings sane. |
bf4735a46 [PATCH] Kconfig r... |
349 |
|
e949f4c2d kbuild: add CONFI... |
350 351 |
config HEADERS_INSTALL bool "Install uapi headers to usr/include" |
bf4735a46 [PATCH] Kconfig r... |
352 353 |
depends on !UML help |
e949f4c2d kbuild: add CONFI... |
354 355 356 357 358 |
This option will install uapi headers (headers exported to user-space) into the usr/include directory for use during the kernel build. This is unneeded for building the kernel itself, but needed for some user-space program samples. It is also needed by some features such as uapi header sanity checks. |
91341d4b2 kbuild: introduce... |
359 360 |
config DEBUG_SECTION_MISMATCH bool "Enable full Section mismatch analysis" |
7d73c3e9c Makefile: remove ... |
361 |
depends on CC_IS_GCC |
91341d4b2 kbuild: introduce... |
362 363 364 |
help The section mismatch analysis checks if there are illegal references from one section to another section. |
e809ab010 Kconfig: Copyedit... |
365 366 |
During linktime or runtime, some sections are dropped; any use of code/data previously in these sections would |
91341d4b2 kbuild: introduce... |
367 |
most likely result in an oops. |
e809ab010 Kconfig: Copyedit... |
368 |
In the code, functions and variables are annotated with |
0db0628d9 kernel: delete __... |
369 |
__init,, etc. (see the full list in include/linux/init.h), |
d6fbfa4fc kbuild: Spelling/... |
370 |
which results in the code/data being placed in specific sections. |
e809ab010 Kconfig: Copyedit... |
371 372 |
The section mismatch analysis is always performed after a full kernel build, and enabling this option causes the following |
b7dca6dd1 kbuild: create *.... |
373 |
additional step to occur: |
e809ab010 Kconfig: Copyedit... |
374 375 376 |
- Add the option -fno-inline-functions-called-once to gcc commands. When inlining a function annotated with __init in a non-init function, we would lose the section information and thus |
91341d4b2 kbuild: introduce... |
377 |
the analysis would not catch the illegal reference. |
e809ab010 Kconfig: Copyedit... |
378 379 |
This option tells gcc to inline less (but it does result in a larger kernel). |
91341d4b2 kbuild: introduce... |
380 |
|
47490ec14 modpost: Add flag... |
381 382 383 384 385 386 387 388 |
config SECTION_MISMATCH_WARN_ONLY bool "Make section mismatch errors non-fatal" default y help If you say N here, the build process will fail if there are any section mismatch, instead of just throwing warnings. If unsure, say Y. |
cf536e185 Makefile: extend ... |
389 |
config DEBUG_FORCE_FUNCTION_ALIGN_64B |
9d849449d lib/Kconfig.debug... |
390 391 |
bool "Force all function address 64B aligned" depends on EXPERT && (X86_64 || ARM64 || PPC32 || PPC64 || ARC) |
09c60546f ./Makefile: add d... |
392 393 394 395 396 397 398 399 |
help There are cases that a commit from one domain changes the function address alignment of other domains, and cause magic performance bump (regression or improvement). Enable this option will help to verify if the bump is caused by function alignment changes, while it will slightly increase the kernel size and affect icache usage. It is mainly for debug and performance tuning use. |
6dfc06651 consolidate compi... |
400 401 402 403 404 405 406 |
# # Select this config option from the architecture Kconfig, if it # is preferred to always offer frame pointers as a config # option on the architecture (regardless of KERNEL_DEBUG): # config ARCH_WANT_FRAME_POINTERS bool |
f346f4b37 [PATCH] let MAGIC... |
407 |
|
6dfc06651 consolidate compi... |
408 409 |
config FRAME_POINTER bool "Compile the kernel with frame pointers" |
a687a5337 treewide: simplif... |
410 |
depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS |
6dfc06651 consolidate compi... |
411 |
default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS |
a304e1b82 [PATCH] Debug sha... |
412 |
help |
6dfc06651 consolidate compi... |
413 414 415 |
If you say Y here the resulting kernel image will be slightly larger and slower, but it gives very useful debugging information in case of kernel bugs. (precise oopses/stacktraces/warnings) |
a304e1b82 [PATCH] Debug sha... |
416 |
|
b9ab5ebb1 objtool: Add CONF... |
417 418 419 420 421 422 423 424 |
config STACK_VALIDATION bool "Compile-time stack metadata validation" depends on HAVE_STACK_VALIDATION default n help Add compile-time checks to validate stack metadata, including frame pointers (if CONFIG_FRAME_POINTER is enabled). This helps ensure that runtime stack traces are more reliable. |
ee9f8fce9 x86/unwind: Add t... |
425 |
This is also a prerequisite for generation of ORC unwind data, which |
11af84744 x86/unwind: Renam... |
426 |
is needed for CONFIG_UNWINDER_ORC. |
ee9f8fce9 x86/unwind: Add t... |
427 |
|
b9ab5ebb1 objtool: Add CONF... |
428 429 |
For more information, see tools/objtool/Documentation/stack-validation.txt. |
6804c1afd kbuild/objtool: A... |
430 431 432 433 |
config VMLINUX_VALIDATION bool depends on STACK_VALIDATION && DEBUG_ENTRY && !PARAVIRT default y |
5cc124720 kbuild: add CONFI... |
434 435 436 437 438 439 440 441 442 |
config VMLINUX_MAP bool "Generate vmlinux.map file when linking" depends on EXPERT help Selecting this option will pass "-Map=vmlinux.map" to ld when linking vmlinux. That file can be useful for verifying and debugging magic section games, and for seeing which pieces of code get eliminated with CONFIG_LD_DEAD_CODE_DATA_ELIMINATION. |
6dfc06651 consolidate compi... |
443 444 445 |
config DEBUG_FORCE_WEAK_PER_CPU bool "Force weak per-cpu definitions" depends on DEBUG_KERNEL |
8446f1d39 [PATCH] detect so... |
446 |
help |
6dfc06651 consolidate compi... |
447 448 449 450 |
s390 and alpha require percpu variables in modules to be defined weak to work around addressing range issue which puts the following two restrictions on percpu variable definitions. |
8446f1d39 [PATCH] detect so... |
451 |
|
6dfc06651 consolidate compi... |
452 453 |
1. percpu symbols must be unique whether static or not 2. percpu variables can't be defined inside a function |
8446f1d39 [PATCH] detect so... |
454 |
|
6dfc06651 consolidate compi... |
455 456 |
To ensure that generic code follows the above rules, this option forces all percpu variables to be defined as weak. |
5f3290894 watchdog: Update ... |
457 |
|
6dfc06651 consolidate compi... |
458 |
endmenu # "Compiler options" |
8446f1d39 [PATCH] detect so... |
459 |
|
6210b6402 kernel-hacking: g... |
460 |
menu "Generic Kernel Debugging Instruments" |
6dfc06651 consolidate compi... |
461 462 463 464 465 466 467 468 469 470 471 |
config MAGIC_SYSRQ bool "Magic SysRq key" depends on !UML help If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you will be able to flush the buffer cache to disk, reboot the system immediately or dump some status information). This is accomplished by pressing various keys while holding SysRq (Alt+PrintScreen). It also works on a serial console (on PC hardware at least), if you send a BREAK and then within 5 seconds a command keypress. The |
f8998c226 lib/Kconfig.debug... |
472 473 |
keys are documented in <file:Documentation/admin-guide/sysrq.rst>. Don't say Y unless you really know what this hack does. |
8446f1d39 [PATCH] detect so... |
474 |
|
8eaede49d sysrq: Allow magi... |
475 476 477 478 479 480 481 |
config MAGIC_SYSRQ_DEFAULT_ENABLE hex "Enable magic SysRq key functions by default" depends on MAGIC_SYSRQ default 0x1 help Specifies which SysRq key functions are enabled by default. This may be set to 1 or 0 to enable or disable them all, or |
f8998c226 lib/Kconfig.debug... |
482 |
to a bitmask as described in Documentation/admin-guide/sysrq.rst. |
8eaede49d sysrq: Allow magi... |
483 |
|
732dbf3a6 serial: do not ac... |
484 485 486 487 488 489 490 491 492 |
config MAGIC_SYSRQ_SERIAL bool "Enable magic SysRq key over serial" depends on MAGIC_SYSRQ default y help Many embedded boards have a disconnected TTL level serial which can generate some garbage that can lead to spurious false sysrq detects. This option allows you to decide whether you want to enable the magic SysRq key. |
68af43173 serial/sysrq: Add... |
493 494 495 496 497 498 499 |
config MAGIC_SYSRQ_SERIAL_SEQUENCE string "Char sequence that enables magic SysRq over serial" depends on MAGIC_SYSRQ_SERIAL default "" help Specifies a sequence of characters that can follow BREAK to enable SysRq on a serial console. |
d3394b3d5 serial/sysrq: Add... |
500 |
If unsure, leave an empty string and the option will not be enabled. |
ec29a5c19 kernel-hacking: m... |
501 502 503 504 505 506 507 508 509 510 511 |
config DEBUG_FS bool "Debug Filesystem" help debugfs is a virtual file system that kernel developers use to put debugging files into. Enable this option to be able to read and write to these files. For detailed documentation on the debugfs API, see Documentation/filesystems/. If unsure, say N. |
a24c6f7bc debugfs: Add acce... |
512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 |
choice prompt "Debugfs default access" depends on DEBUG_FS default DEBUG_FS_ALLOW_ALL help This selects the default access restrictions for debugfs. It can be overridden with kernel command line option debugfs=[on,no-mount,off]. The restrictions apply for API access and filesystem registration. config DEBUG_FS_ALLOW_ALL bool "Access normal" help No restrictions apply. Both API and filesystem registration is on. This is the normal default operation. config DEBUG_FS_DISALLOW_MOUNT bool "Do not register debugfs as filesystem" help The API is open but filesystem is not loaded. Clients can still do their work and read with debug tools that do not need debugfs filesystem. config DEBUG_FS_ALLOW_NONE bool "No access" help Access is off. Clients get -PERM when trying to create nodes in debugfs tree and debugfs is not registered as a filesystem. Client can then back-off or continue without debugfs access. endchoice |
6210b6402 kernel-hacking: g... |
543 |
source "lib/Kconfig.kgdb" |
6210b6402 kernel-hacking: g... |
544 |
source "lib/Kconfig.ubsan" |
2645d4320 kcsan: kconfig: m... |
545 |
source "lib/Kconfig.kcsan" |
6210b6402 kernel-hacking: g... |
546 547 |
endmenu |
f346f4b37 [PATCH] let MAGIC... |
548 549 |
config DEBUG_KERNEL bool "Kernel debugging" |
fef2c9bc1 kernel/watchdog.c... |
550 |
help |
f346f4b37 [PATCH] let MAGIC... |
551 552 |
Say Y here if you are developing drivers or trying to debug and identify kernel problems. |
fef2c9bc1 kernel/watchdog.c... |
553 |
|
c66d7a27b init: introduce D... |
554 555 556 557 558 559 560 |
config DEBUG_MISC bool "Miscellaneous debug code" default DEBUG_KERNEL depends on DEBUG_KERNEL help Say Y here if you need to enable miscellaneous debug code that should be under a more specific debug option but isn't. |
0610c8a8a order memory debu... |
561 |
menu "Memory Debugging" |
fef2c9bc1 kernel/watchdog.c... |
562 |
|
8636a1f96 treewide: surroun... |
563 |
source "mm/Kconfig.debug" |
fef2c9bc1 kernel/watchdog.c... |
564 |
|
0610c8a8a order memory debu... |
565 566 567 |
config DEBUG_OBJECTS bool "Debug object operations" depends on DEBUG_KERNEL |
9c44bc03f softlockup: allow... |
568 |
help |
0610c8a8a order memory debu... |
569 570 571 |
If you say Y here, additional code will be inserted into the kernel to track the life time of various objects and validate the operations on those objects. |
9c44bc03f softlockup: allow... |
572 |
|
0610c8a8a order memory debu... |
573 574 575 576 577 |
config DEBUG_OBJECTS_SELFTEST bool "Debug objects selftest" depends on DEBUG_OBJECTS help This enables the selftest of the object debug code. |
9c44bc03f softlockup: allow... |
578 |
|
0610c8a8a order memory debu... |
579 580 581 582 583 584 585 586 |
config DEBUG_OBJECTS_FREE bool "Debug objects in freed memory" depends on DEBUG_OBJECTS help This enables checks whether a k/v free operation frees an area which contains an object which has not been deactivated properly. This can make kmalloc/kfree-intensive workloads much slower. |
3ac7fe5a4 infrastructure to... |
587 |
|
c6f3a97f8 debugobjects: add... |
588 589 590 591 592 593 594 |
config DEBUG_OBJECTS_TIMERS bool "Debug timer objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the timer routines to track the life time of timer objects and validate the timer operations. |
dc186ad74 workqueue: Add de... |
595 596 597 598 599 600 601 |
config DEBUG_OBJECTS_WORK bool "Debug work objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the work queue routines to track the life time of work objects and validate the work operations. |
551d55a94 tree/tiny rcu: Ad... |
602 603 |
config DEBUG_OBJECTS_RCU_HEAD bool "Debug RCU callbacks objects" |
fc2ecf7ec rcu: Enable DEBUG... |
604 |
depends on DEBUG_OBJECTS |
551d55a94 tree/tiny rcu: Ad... |
605 606 |
help Enable this to turn on debugging of RCU list heads (call_rcu() usage). |
e2852ae82 percpu_counter: a... |
607 608 609 610 611 612 613 |
config DEBUG_OBJECTS_PERCPU_COUNTER bool "Debug percpu counter objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the percpu counter routines to track the life time of percpu counter objects and validate the percpu counter operations. |
3ae702054 debugobjects: add... |
614 615 |
config DEBUG_OBJECTS_ENABLE_DEFAULT int "debug_objects bootup default value (0-1)" |
68d4b3dfc lib/: fix Kconfig... |
616 617 618 619 620 |
range 0 1 default "1" depends on DEBUG_OBJECTS help Debug objects boot parameter default value |
3ae702054 debugobjects: add... |
621 |
|
1da177e4c Linux-2.6.12-rc2 |
622 |
config DEBUG_SLAB |
4a2f0acf0 [PATCH] kconfig: ... |
623 |
bool "Debug slab memory allocations" |
4675ff05d kmemcheck: rip it... |
624 |
depends on DEBUG_KERNEL && SLAB |
1da177e4c Linux-2.6.12-rc2 |
625 626 627 628 |
help Say Y here to have the kernel do limited verification on memory allocation as well as poisoning memory on free to catch use of freed memory. This can make kmalloc/kfree-intensive workloads much slower. |
f0630fff5 SLUB: support slu... |
629 630 |
config SLUB_DEBUG_ON bool "SLUB debugging on by default" |
4675ff05d kmemcheck: rip it... |
631 |
depends on SLUB && SLUB_DEBUG |
f0630fff5 SLUB: support slu... |
632 633 634 635 636 637 638 639 640 |
default n help Boot with debugging on by default. SLUB boots by default with the runtime debug capabilities switched off. Enabling this is equivalent to specifying the "slub_debug" parameter on boot. There is no support for more fine grained debug control like possible with slub_debug=xxx. SLUB debugging may be switched off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying "slub_debug=-". |
8ff12cfc0 SLUB: Support for... |
641 642 643 |
config SLUB_STATS default n bool "Enable SLUB performance statistics" |
ab4d5ed5e slub: Enable sysf... |
644 |
depends on SLUB && SYSFS |
8ff12cfc0 SLUB: Support for... |
645 646 647 648 649 650 651 652 |
help SLUB statistics are useful to debug SLUBs allocation behavior in order find ways to optimize the allocator. This should never be enabled for production use since keeping statistics slows down the allocator by a few percentage points. The slabinfo command supports the determination of the most active slabs to figure out which slabs are relevant to a particular load. Try running: slabinfo -DA |
b69ec42b1 Kconfig: clean up... |
653 654 |
config HAVE_DEBUG_KMEMLEAK bool |
3bba00d7b kmemleak: Enable ... |
655 656 |
config DEBUG_KMEMLEAK bool "Kernel memory leak detector" |
525c1f920 lib: remove depen... |
657 |
depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK |
79e0d9bd2 kmemleak: Select ... |
658 |
select DEBUG_FS |
3bba00d7b kmemleak: Enable ... |
659 660 |
select STACKTRACE if STACKTRACE_SUPPORT select KALLSYMS |
b60e26a2f kmemleak: fix kco... |
661 |
select CRC32 |
3bba00d7b kmemleak: Enable ... |
662 663 664 665 666 667 668 |
help Say Y here if you want to enable the memory leak detector. The memory allocation/freeing is traced in a way similar to the Boehm's conservative garbage collector, the difference being that the orphan objects are not freed but only shown in /sys/kernel/debug/kmemleak. Enabling this feature will introduce an overhead to memory |
700199b0c Kconfig: lib/Kcon... |
669 |
allocations. See Documentation/dev-tools/kmemleak.rst for more |
3bba00d7b kmemleak: Enable ... |
670 |
details. |
0610c8a8a order memory debu... |
671 672 673 674 675 |
Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances of finding leaks due to the slab objects poisoning. In order to access the kmemleak file, debugfs needs to be mounted (usually at /sys/kernel/debug). |
c56658681 mm: kmemleak: use... |
676 677 |
config DEBUG_KMEMLEAK_MEM_POOL_SIZE int "Kmemleak memory pool size" |
0610c8a8a order memory debu... |
678 |
depends on DEBUG_KMEMLEAK |
c59180ae3 mm/kmemleak: incr... |
679 |
range 200 1000000 |
b751c52bb kmemleak: increas... |
680 |
default 16000 |
0610c8a8a order memory debu... |
681 682 683 |
help Kmemleak must track all the memory allocations to avoid reporting false positives. Since memory may be allocated or |
c56658681 mm: kmemleak: use... |
684 685 686 687 |
freed before kmemleak is fully initialised, use a static pool of metadata objects to track such callbacks. After kmemleak is fully initialised, this memory pool acts as an emergency one if slab allocations fail. |
0610c8a8a order memory debu... |
688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 |
config DEBUG_KMEMLEAK_TEST tristate "Simple test for the kernel memory leak detector" depends on DEBUG_KMEMLEAK && m help This option enables a module that explicitly leaks memory. If unsure, say N. config DEBUG_KMEMLEAK_DEFAULT_OFF bool "Default kmemleak to off" depends on DEBUG_KMEMLEAK help Say Y here to disable kmemleak by default. It can then be enabled on the command line via kmemleak=on. |
d53ce0422 kmemleak: add con... |
703 704 705 706 707 708 709 710 711 712 713 714 715 716 |
config DEBUG_KMEMLEAK_AUTO_SCAN bool "Enable kmemleak auto scan thread on boot up" default y depends on DEBUG_KMEMLEAK help Depending on the cpu, kmemleak scan may be cpu intensive and can stall user tasks at times. This option enables/disables automatic kmemleak scan at boot up. Say N here to disable kmemleak auto scan thread to stop automatic scanning. Disabling this option disables automatic reporting of memory leaks. If unsure, say Y. |
0610c8a8a order memory debu... |
717 718 |
config DEBUG_STACK_USAGE bool "Stack utilization instrumentation" |
6c31da346 parisc,metag: Imp... |
719 |
depends on DEBUG_KERNEL && !IA64 |
0610c8a8a order memory debu... |
720 721 722 723 724 |
help Enables the display of the minimum amount of free stack which each task has ever had available in the sysrq-T and sysrq-P debug output. This option will slow down process creation somewhat. |
dc9b96387 kernel-hacking: m... |
725 726 727 728 729 730 731 732 733 734 735 |
config SCHED_STACK_END_CHECK bool "Detect stack corruption on calls to schedule()" depends on DEBUG_KERNEL default n help This option checks for a stack overrun on calls to schedule(). If the stack end location is found to be over written always panic as the content of the corrupted region can no longer be trusted. This is to ensure no erroneous behaviour occurs which could result in data corruption or a sporadic crash at a later stage once the region is examined. The runtime overhead introduced is minimal. |
399145f9e mm/debug: add tes... |
736 737 738 739 740 |
config ARCH_HAS_DEBUG_VM_PGTABLE bool help An architecture should select this when it can successfully build and run DEBUG_VM_PGTABLE. |
0610c8a8a order memory debu... |
741 742 743 744 745 |
config DEBUG_VM bool "Debug VM" depends on DEBUG_KERNEL help Enable this to turn on extended checks in the virtual-memory system |
68d4b3dfc lib/: fix Kconfig... |
746 |
that may impact performance. |
0610c8a8a order memory debu... |
747 748 |
If unsure, say N. |
4f115147f mm,vmacache: add ... |
749 750 751 752 753 754 755 756 757 |
config DEBUG_VM_VMACACHE bool "Debug VMA caching" depends on DEBUG_VM help Enable this to turn on VMA caching debug information. Doing so can cause significant overhead, so only enable it in non-production environments. If unsure, say N. |
0610c8a8a order memory debu... |
758 759 760 761 |
config DEBUG_VM_RB bool "Debug VM red-black trees" depends on DEBUG_VM help |
a663dad65 mm: fix CONFIG_DE... |
762 |
Enable VM red-black tree debugging information and extra validations. |
0610c8a8a order memory debu... |
763 764 |
If unsure, say N. |
95ad97554 page-flags: intro... |
765 766 767 768 769 770 771 |
config DEBUG_VM_PGFLAGS bool "Debug page-flags operations" depends on DEBUG_VM help Enables extra validation on page flags operations. If unsure, say N. |
399145f9e mm/debug: add tes... |
772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 |
config DEBUG_VM_PGTABLE bool "Debug arch page table for semantics compliance" depends on MMU depends on ARCH_HAS_DEBUG_VM_PGTABLE default y if DEBUG_VM help This option provides a debug method which can be used to test architecture page table helper functions on various platforms in verifying if they comply with expected generic MM semantics. This will help architecture code in making sure that any changes or new additions of these helpers still conform to expected semantics of the generic MM. Platforms will have to opt in for this through ARCH_HAS_DEBUG_VM_PGTABLE. If unsure, say N. |
fa5b6ec9e lib/Kconfig.debug... |
787 788 |
config ARCH_HAS_DEBUG_VIRTUAL bool |
0610c8a8a order memory debu... |
789 790 |
config DEBUG_VIRTUAL bool "Debug VM translations" |
fa5b6ec9e lib/Kconfig.debug... |
791 |
depends on DEBUG_KERNEL && ARCH_HAS_DEBUG_VIRTUAL |
0610c8a8a order memory debu... |
792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 |
help Enable some costly sanity checks in virtual to page code. This can catch mistakes with virt_to_page() and friends. If unsure, say N. config DEBUG_NOMMU_REGIONS bool "Debug the global anon/private NOMMU mapping region tree" depends on DEBUG_KERNEL && !MMU help This option causes the global tree of anonymous and private mapping regions to be regularly checked for invalid topology. config DEBUG_MEMORY_INIT bool "Debug memory initialisation" if EXPERT default !EXPERT help Enable this for additional checks during memory initialisation. The sanity checks verify aspects of the VM such as the memory model and other information provided by the architecture. Verbose information will be printed at KERN_DEBUG loglevel depending on the mminit_loglevel= command-line option. If unsure, say Y config MEMORY_NOTIFIER_ERROR_INJECT tristate "Memory hotplug notifier error injection module" depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION help This option provides the ability to inject artificial errors to memory hotplug notifier chain callbacks. It is controlled through debugfs interface under /sys/kernel/debug/notifier-error-inject/memory If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject memory hotplug offline error (-12 == -ENOMEM) # cd /sys/kernel/debug/notifier-error-inject/memory # echo -12 > actions/MEM_GOING_OFFLINE/error # echo offline > /sys/devices/system/memory/memoryXXX/state bash: echo: write error: Cannot allocate memory To compile this code as a module, choose M here: the module will be called memory-notifier-error-inject. If unsure, say N. config DEBUG_PER_CPU_MAPS bool "Debug access to per_cpu maps" depends on DEBUG_KERNEL depends on SMP help Say Y to verify that the per_cpu map being accessed has been set up. This adds a fair amount of code to kernel memory and decreases performance. Say N if unsure. |
6e799cb69 mm/highmem: Provi... |
850 851 852 853 854 855 |
config DEBUG_KMAP_LOCAL bool "Debug kmap_local temporary mappings" depends on DEBUG_KERNEL && KMAP_LOCAL help This option enables additional error checking for the kmap_local infrastructure. Disable for production use. |
0e91a0c69 mm/highmem: Provi... |
856 857 858 859 860 861 862 863 864 865 866 867 |
config ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP bool config DEBUG_KMAP_LOCAL_FORCE_MAP bool "Enforce kmap_local temporary mappings" depends on DEBUG_KERNEL && ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP select KMAP_LOCAL select DEBUG_KMAP_LOCAL help This option enforces temporary mappings through the kmap_local mechanism for non-highmem pages and on non-highmem systems. Disable this for production systems! |
0610c8a8a order memory debu... |
868 869 870 |
config DEBUG_HIGHMEM bool "Highmem debugging" depends on DEBUG_KERNEL && HIGHMEM |
0e91a0c69 mm/highmem: Provi... |
871 |
select DEBUG_KMAP_LOCAL_FORCE_MAP if ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP |
6e799cb69 mm/highmem: Provi... |
872 |
select DEBUG_KMAP_LOCAL |
0610c8a8a order memory debu... |
873 |
help |
b1357c9f6 Kconfig.debug: Gr... |
874 875 |
This option enables additional error checking for high memory systems. Disable for production systems. |
0610c8a8a order memory debu... |
876 877 878 879 880 881 882 |
config HAVE_DEBUG_STACKOVERFLOW bool config DEBUG_STACKOVERFLOW bool "Check for stack overflows" depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW |
a7f7f6248 treewide: replace... |
883 |
help |
0610c8a8a order memory debu... |
884 |
Say Y here if you want to check for overflows of kernel, IRQ |
edb0ec072 kexec, Kconfig: s... |
885 |
and exception stacks (if your architecture uses them). This |
0610c8a8a order memory debu... |
886 887 888 889 890 891 892 893 894 895 896 |
option will show detailed messages if free stack space drops below a certain limit. These kinds of bugs usually occur when call-chains in the kernel get too deep, especially when interrupts are involved. Use this in cases where you see apparently random memory corruption, especially if it appears in 'struct thread_info' If in doubt, say "N". |
0b24becc8 kasan: add kernel... |
897 |
source "lib/Kconfig.kasan" |
0ce20dd84 mm: add Kernel El... |
898 |
source "lib/Kconfig.kfence" |
0b24becc8 kasan: add kernel... |
899 |
|
0610c8a8a order memory debu... |
900 |
endmenu # "Memory Debugging" |
a304e1b82 [PATCH] Debug sha... |
901 902 |
config DEBUG_SHIRQ bool "Debug shared IRQ handlers" |
0244ad004 Remove GENERIC_HA... |
903 |
depends on DEBUG_KERNEL |
a304e1b82 [PATCH] Debug sha... |
904 |
help |
0a2fae2ae lib: update DEBUG... |
905 906 907 908 |
Enable this to generate a spurious interrupt just before a shared interrupt handler is deregistered (generating one when registering is currently disabled). Drivers need to handle this correctly. Some don't and need to be caught. |
a304e1b82 [PATCH] Debug sha... |
909 |
|
f43a289df kernel-hacking: m... |
910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 |
menu "Debug Oops, Lockups and Hangs" config PANIC_ON_OOPS bool "Panic on Oops" help Say Y here to enable the kernel to panic when it oopses. This has the same effect as setting oops=panic on the kernel command line. This feature is useful to ensure that the kernel does not do anything erroneous after an oops which could result in data corruption or other issues. Say N if unsure. config PANIC_ON_OOPS_VALUE int range 0 1 default 0 if !PANIC_ON_OOPS default 1 if PANIC_ON_OOPS config PANIC_TIMEOUT int "panic timeout" default 0 help |
9d5b134f9 lib/Kconfig.debug... |
935 |
Set the timeout value (in seconds) until a reboot occurs when |
f43a289df kernel-hacking: m... |
936 937 938 |
the kernel panics. If n = 0, then we wait forever. A timeout value n > 0 will wait n seconds before rebooting, while a timeout value n < 0 will reboot immediately. |
92aef8fba hang and lockup d... |
939 |
|
58687acba lockup_detector: ... |
940 |
config LOCKUP_DETECTOR |
05a4a9527 kernel/watchdog: ... |
941 942 943 944 |
bool config SOFTLOCKUP_DETECTOR bool "Detect Soft Lockups" |
dea20a3fb [PATCH] Disable D... |
945 |
depends on DEBUG_KERNEL && !S390 |
05a4a9527 kernel/watchdog: ... |
946 |
select LOCKUP_DETECTOR |
8446f1d39 [PATCH] detect so... |
947 |
help |
58687acba lockup_detector: ... |
948 |
Say Y here to enable the kernel to act as a watchdog to detect |
05a4a9527 kernel/watchdog: ... |
949 |
soft lockups. |
58687acba lockup_detector: ... |
950 951 |
Softlockups are bugs that cause the kernel to loop in kernel |
5f3290894 watchdog: Update ... |
952 |
mode for more than 20 seconds, without giving other tasks a |
58687acba lockup_detector: ... |
953 954 |
chance to run. The current stack trace is displayed upon detection and the system will stay locked up. |
8446f1d39 [PATCH] detect so... |
955 |
|
5f00ae0d3 lib/Kconfig.debug... |
956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 |
config BOOTPARAM_SOFTLOCKUP_PANIC bool "Panic (Reboot) On Soft Lockups" depends on SOFTLOCKUP_DETECTOR help Say Y here to enable the kernel to panic on "soft lockups", which are bugs that cause the kernel to loop in kernel mode for more than 20 seconds (configurable using the watchdog_thresh sysctl), without giving other tasks a chance to run. The panic can be used in combination with panic_timeout, to cause the system to reboot automatically after a lockup has been detected. This feature is useful for high-availability systems that have uptime guarantees and where a lockup must be resolved ASAP. Say N if unsure. config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE int depends on SOFTLOCKUP_DETECTOR range 0 1 default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC default 1 if BOOTPARAM_SOFTLOCKUP_PANIC |
05a4a9527 kernel/watchdog: ... |
979 980 981 982 983 |
config HARDLOCKUP_DETECTOR_PERF bool select SOFTLOCKUP_DETECTOR # |
7edaeb684 kernel/watchdog: ... |
984 985 986 987 988 989 990 |
# Enables a timestamp based low pass filter to compensate for perf based # hard lockup detection which runs too fast due to turbo modes. # config HARDLOCKUP_CHECK_TIMESTAMP bool # |
05a4a9527 kernel/watchdog: ... |
991 992 993 994 995 996 997 998 999 |
# arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard # lockup detector rather than the perf based detector. # config HARDLOCKUP_DETECTOR bool "Detect Hard Lockups" depends on DEBUG_KERNEL && !S390 depends on HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_ARCH select LOCKUP_DETECTOR select HARDLOCKUP_DETECTOR_PERF if HAVE_HARDLOCKUP_DETECTOR_PERF |
05a4a9527 kernel/watchdog: ... |
1000 1001 1002 |
help Say Y here to enable the kernel to act as a watchdog to detect hard lockups. |
58687acba lockup_detector: ... |
1003 |
Hardlockups are bugs that cause the CPU to loop in kernel mode |
5f3290894 watchdog: Update ... |
1004 |
for more than 10 seconds, without letting other interrupts have a |
58687acba lockup_detector: ... |
1005 1006 |
chance to run. The current stack trace is displayed upon detection and the system will stay locked up. |
8446f1d39 [PATCH] detect so... |
1007 |
|
fef2c9bc1 kernel/watchdog.c... |
1008 1009 |
config BOOTPARAM_HARDLOCKUP_PANIC bool "Panic (Reboot) On Hard Lockups" |
8f1f66ed7 lib/Kconfig.debug... |
1010 |
depends on HARDLOCKUP_DETECTOR |
fef2c9bc1 kernel/watchdog.c... |
1011 1012 1013 |
help Say Y here to enable the kernel to panic on "hard lockups", which are bugs that cause the kernel to loop in kernel |
5f3290894 watchdog: Update ... |
1014 1015 |
mode with interrupts disabled for more than 10 seconds (configurable using the watchdog_thresh sysctl). |
fef2c9bc1 kernel/watchdog.c... |
1016 1017 1018 1019 1020 |
Say N if unsure. config BOOTPARAM_HARDLOCKUP_PANIC_VALUE int |
8f1f66ed7 lib/Kconfig.debug... |
1021 |
depends on HARDLOCKUP_DETECTOR |
fef2c9bc1 kernel/watchdog.c... |
1022 1023 1024 |
range 0 1 default 0 if !BOOTPARAM_HARDLOCKUP_PANIC default 1 if BOOTPARAM_HARDLOCKUP_PANIC |
e162b39a3 softlockup: decou... |
1025 1026 1027 |
config DETECT_HUNG_TASK bool "Detect Hung Tasks" depends on DEBUG_KERNEL |
05a4a9527 kernel/watchdog: ... |
1028 |
default SOFTLOCKUP_DETECTOR |
e162b39a3 softlockup: decou... |
1029 |
help |
0610c8a8a order memory debu... |
1030 1031 |
Say Y here to enable the kernel to detect "hung tasks", which are bugs that cause the task to be stuck in |
96b03ab86 locking/hung_task... |
1032 |
uninterruptible "D" state indefinitely. |
1da177e4c Linux-2.6.12-rc2 |
1033 |
|
0610c8a8a order memory debu... |
1034 1035 1036 1037 1038 |
When a hung task is detected, the kernel will print the current stack trace (which you should report), but the task will stay in uninterruptible state. If lockdep is enabled then all held locks will also be reported. This feature has negligible overhead. |
871751e25 [PATCH] slab: imp... |
1039 |
|
0610c8a8a order memory debu... |
1040 1041 1042 1043 |
config DEFAULT_HUNG_TASK_TIMEOUT int "Default timeout for hung task detection (in seconds)" depends on DETECT_HUNG_TASK default 120 |
f0630fff5 SLUB: support slu... |
1044 |
help |
0610c8a8a order memory debu... |
1045 1046 1047 |
This option controls the default timeout (in seconds) used to determine when a task has become non-responsive and should be considered hung. |
f0630fff5 SLUB: support slu... |
1048 |
|
0610c8a8a order memory debu... |
1049 1050 1051 |
It can be adjusted at runtime via the kernel.hung_task_timeout_secs sysctl or by writing a value to /proc/sys/kernel/hung_task_timeout_secs. |
8ff12cfc0 SLUB: Support for... |
1052 |
|
0610c8a8a order memory debu... |
1053 1054 |
A timeout of 0 disables the check. The default is two minutes. Keeping the default should be fine in most cases. |
b69ec42b1 Kconfig: clean up... |
1055 |
|
0610c8a8a order memory debu... |
1056 1057 1058 |
config BOOTPARAM_HUNG_TASK_PANIC bool "Panic (Reboot) On Hung Tasks" depends on DETECT_HUNG_TASK |
3bba00d7b kmemleak: Enable ... |
1059 |
help |
0610c8a8a order memory debu... |
1060 1061 1062 |
Say Y here to enable the kernel to panic on "hung tasks", which are bugs that cause the kernel to leave a task stuck in uninterruptible "D" state. |
3bba00d7b kmemleak: Enable ... |
1063 |
|
0610c8a8a order memory debu... |
1064 1065 1066 1067 1068 |
The panic can be used in combination with panic_timeout, to cause the system to reboot automatically after a hung task has been detected. This feature is useful for high-availability systems that have uptime guarantees and where a hung tasks must be resolved ASAP. |
bf96d1e3e kmemleak: Do not ... |
1069 |
|
0610c8a8a order memory debu... |
1070 |
Say N if unsure. |
bf96d1e3e kmemleak: Do not ... |
1071 |
|
0610c8a8a order memory debu... |
1072 1073 1074 1075 1076 1077 |
config BOOTPARAM_HUNG_TASK_PANIC_VALUE int depends on DETECT_HUNG_TASK range 0 1 default 0 if !BOOTPARAM_HUNG_TASK_PANIC default 1 if BOOTPARAM_HUNG_TASK_PANIC |
3bba00d7b kmemleak: Enable ... |
1078 |
|
82607adcf workqueue: implem... |
1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 |
config WQ_WATCHDOG bool "Detect Workqueue Stalls" depends on DEBUG_KERNEL help Say Y here to enable stall detection on workqueues. If a worker pool doesn't make forward progress on a pending work item for over a given amount of time, 30s by default, a warning message is printed along with dump of workqueue state. This can be configured through kernel parameter "workqueue.watchdog_thresh" and its sysfs counterpart. |
30428ef5d lib/test_lockup: ... |
1089 1090 |
config TEST_LOCKUP tristate "Test module to generate lockups" |
63646bc9f lib/Kconfig.debug... |
1091 |
depends on m |
30428ef5d lib/test_lockup: ... |
1092 1093 1094 1095 1096 1097 1098 1099 1100 |
help This builds the "test_lockup" module that helps to make sure that watchdogs and lockup detectors are working properly. Depending on module parameters it could emulate soft or hard lockup, "hung task", or locking arbitrary lock for a long time. Also it could generate series of lockups with cooling-down periods. If unsure, say N. |
92aef8fba hang and lockup d... |
1101 |
endmenu # "Debug lockups and hangs" |
ebebdd095 kernel-hacking: c... |
1102 |
menu "Scheduler Debugging" |
5800dc3cf panic: Make panic... |
1103 |
|
0610c8a8a order memory debu... |
1104 1105 1106 1107 |
config SCHED_DEBUG bool "Collect scheduler debugging info" depends on DEBUG_KERNEL && PROC_FS default y |
0822ee4ac kmemleak: Simple ... |
1108 |
help |
0610c8a8a order memory debu... |
1109 1110 1111 |
If you say Y here, the /proc/sched_debug file will be provided that can help debug the scheduler. The runtime overhead of this option is minimal. |
0822ee4ac kmemleak: Simple ... |
1112 |
|
f6db83479 sched/stat: Simpl... |
1113 1114 1115 |
config SCHED_INFO bool default n |
0610c8a8a order memory debu... |
1116 1117 1118 |
config SCHEDSTATS bool "Collect scheduler statistics" depends on DEBUG_KERNEL && PROC_FS |
f6db83479 sched/stat: Simpl... |
1119 |
select SCHED_INFO |
0610c8a8a order memory debu... |
1120 1121 1122 1123 1124 1125 1126 1127 |
help If you say Y here, additional code will be inserted into the scheduler and related routines to collect statistics about scheduler behavior and provide them in /proc/schedstat. These stats may be useful for both tuning and debugging the scheduler If you aren't debugging the scheduler or trying to tune a specific application, you can say N to avoid the very slight overhead this adds. |
0822ee4ac kmemleak: Simple ... |
1128 |
|
ebebdd095 kernel-hacking: c... |
1129 |
endmenu |
0d9e26329 sched: Add defaul... |
1130 |
|
3c17ad19f timekeeping: Add ... |
1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 |
config DEBUG_TIMEKEEPING bool "Enable extra timekeeping sanity checking" help This option will enable additional timekeeping sanity checks which may be helpful when diagnosing issues where timekeeping problems are suspected. This may include checks in the timekeeping hotpaths, so this option may have a (very small) performance impact to some workloads. If unsure, say N. |
1da177e4c Linux-2.6.12-rc2 |
1143 1144 |
config DEBUG_PREEMPT bool "Debug preemptible kernel" |
9f4728692 sched/core: Use C... |
1145 |
depends on DEBUG_KERNEL && PREEMPTION && TRACE_IRQFLAGS_SUPPORT |
1da177e4c Linux-2.6.12-rc2 |
1146 1147 1148 1149 1150 1151 |
default y help If you say Y here then the kernel will use a debug variant of the commonly used smp_processor_id() function and will print warnings if kernel code uses it in a preemption-unsafe way. Also, the kernel will detect preemption count underflows. |
9eade16b4 group locking deb... |
1152 |
menu "Lock Debugging (spinlocks, mutexes, etc...)" |
f07cbebb6 locking/Kconfig: ... |
1153 1154 1155 1156 |
config LOCK_DEBUGGING_SUPPORT bool depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT default y |
19193bcad locking/Kconfig: ... |
1157 1158 1159 1160 1161 |
config PROVE_LOCKING bool "Lock debugging: prove locking correctness" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select LOCKDEP select DEBUG_SPINLOCK |
bb630f9f7 locking/rtmutex: ... |
1162 |
select DEBUG_MUTEXES if !PREEMPT_RT |
19193bcad locking/Kconfig: ... |
1163 |
select DEBUG_RT_MUTEXES if RT_MUTEXES |
c71fd893f locking/rwsem: Ma... |
1164 |
select DEBUG_RWSEMS |
19193bcad locking/Kconfig: ... |
1165 1166 |
select DEBUG_WW_MUTEX_SLOWPATH select DEBUG_LOCK_ALLOC |
8fd8ad5c5 lockdep: Add pree... |
1167 |
select PREEMPT_COUNT if !ARCH_NO_PREEMPT |
19193bcad locking/Kconfig: ... |
1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 |
select TRACE_IRQFLAGS default n help This feature enables the kernel to prove that all locking that occurs in the kernel runtime is mathematically correct: that under no circumstance could an arbitrary (and not yet triggered) combination of observed locking sequences (on an arbitrary number of CPUs, running an arbitrary number of tasks and interrupt contexts) cause a deadlock. In short, this feature enables the kernel to report locking related deadlocks before they actually occur. The proof does not depend on how hard and complex a deadlock scenario would be to trigger: how many participant CPUs, tasks and irq-contexts would be needed for it to trigger. The proof also does not depend on timing: if a race and a resulting deadlock is possible theoretically (no matter how unlikely the race scenario is), it will be proven so and will immediately be reported by the kernel (once the event is observed that makes the deadlock theoretically possible). If a deadlock is impossible (i.e. the locking rules, as observed by the kernel, are mathematically correct), the kernel reports nothing. NOTE: this feature can also be enabled for rwlocks, mutexes and rwsems - in which case all dependencies between these different locking variants are observed and mapped too, and the proof of observed correctness is also maintained for an arbitrary combination of these separate locking variants. |
387b14684 docs: locking: co... |
1201 |
For more details, see Documentation/locking/lockdep-design.rst. |
19193bcad locking/Kconfig: ... |
1202 |
|
de8f5e4f2 lockdep: Introduc... |
1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 |
config PROVE_RAW_LOCK_NESTING bool "Enable raw_spinlock - spinlock nesting checks" depends on PROVE_LOCKING default n help Enable the raw_spinlock vs. spinlock nesting checks which ensure that the lock nesting rules for PREEMPT_RT enabled kernels are not violated. NOTE: There are known nesting problems. So if you enable this option expect lockdep splats until these problems have been fully addressed which is work in progress. This config switch allows to identify and analyze these problems. It will be removed and the |
9dbbc3b9d lib: fix spelling... |
1216 |
check permanently enabled once the main issues have been fixed. |
de8f5e4f2 lockdep: Introduc... |
1217 1218 |
If unsure, select N. |
19193bcad locking/Kconfig: ... |
1219 1220 1221 1222 1223 |
config LOCK_STAT bool "Lock usage statistics" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select LOCKDEP select DEBUG_SPINLOCK |
bb630f9f7 locking/rtmutex: ... |
1224 |
select DEBUG_MUTEXES if !PREEMPT_RT |
19193bcad locking/Kconfig: ... |
1225 1226 1227 1228 1229 |
select DEBUG_RT_MUTEXES if RT_MUTEXES select DEBUG_LOCK_ALLOC default n help This feature enables tracking lock contention points |
387b14684 docs: locking: co... |
1230 |
For more details, see Documentation/locking/lockstat.rst |
19193bcad locking/Kconfig: ... |
1231 1232 1233 1234 1235 1236 1237 1238 |
This also enables lock events required by "perf lock", subcommand of perf. If you want to use "perf lock", you also need to turn on CONFIG_EVENT_TRACING. CONFIG_LOCK_STAT defines "contended" and "acquired" lock events. (CONFIG_LOCKDEP defines "acquire" and "release" events.) |
e7eebaf6a [PATCH] pi-futex:... |
1239 1240 |
config DEBUG_RT_MUTEXES bool "RT Mutex debugging, deadlock detection" |
e7eebaf6a [PATCH] pi-futex:... |
1241 1242 1243 1244 |
depends on DEBUG_KERNEL && RT_MUTEXES help This allows rt mutex semantics violations and rt mutex related deadlocks (lockups) to be detected and reported automatically. |
1da177e4c Linux-2.6.12-rc2 |
1245 |
config DEBUG_SPINLOCK |
4d9f34ad3 [PATCH] lockdep: ... |
1246 |
bool "Spinlock and rw-lock debugging: basic checks" |
1da177e4c Linux-2.6.12-rc2 |
1247 |
depends on DEBUG_KERNEL |
e335e3eb8 locking/kconfig: ... |
1248 |
select UNINLINE_SPIN_UNLOCK |
1da177e4c Linux-2.6.12-rc2 |
1249 1250 1251 1252 1253 |
help Say Y here and build SMP to catch missing spinlock initialization and certain other kinds of spinlock errors commonly made. This is best used in conjunction with the NMI watchdog so that spinlock deadlocks are also debuggable. |
4d9f34ad3 [PATCH] lockdep: ... |
1254 1255 |
config DEBUG_MUTEXES bool "Mutex debugging: basic checks" |
bb630f9f7 locking/rtmutex: ... |
1256 |
depends on DEBUG_KERNEL && !PREEMPT_RT |
4d9f34ad3 [PATCH] lockdep: ... |
1257 1258 1259 |
help This feature allows mutex semantics violations to be detected and reported. |
230100276 mutex: Add w/w mu... |
1260 1261 |
config DEBUG_WW_MUTEX_SLOWPATH bool "Wait/wound mutex debugging: Slowpath testing" |
f07cbebb6 locking/Kconfig: ... |
1262 |
depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
230100276 mutex: Add w/w mu... |
1263 1264 |
select DEBUG_LOCK_ALLOC select DEBUG_SPINLOCK |
bb630f9f7 locking/rtmutex: ... |
1265 1266 |
select DEBUG_MUTEXES if !PREEMPT_RT select DEBUG_RT_MUTEXES if PREEMPT_RT |
230100276 mutex: Add w/w mu... |
1267 1268 1269 1270 1271 1272 |
help This feature enables slowpath testing for w/w mutex users by injecting additional -EDEADLK wound/backoff cases. Together with the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this will test all possible w/w mutex interface abuse with the exception of simply not acquiring all the required locks. |
4d6923733 ww-mutex: clarify... |
1273 1274 1275 1276 |
Note that this feature can introduce significant overhead, so it really should not be enabled in a production or distro kernel, even a debug kernel. If you are a driver writer, enable it. If you are a distro, do not. |
230100276 mutex: Add w/w mu... |
1277 |
|
5149cbac4 locking/rwsem: Ad... |
1278 1279 |
config DEBUG_RWSEMS bool "RW Semaphore debugging: basic checks" |
c71fd893f locking/rwsem: Ma... |
1280 |
depends on DEBUG_KERNEL |
5149cbac4 locking/rwsem: Ad... |
1281 |
help |
c71fd893f locking/rwsem: Ma... |
1282 1283 |
This debugging feature allows mismatched rw semaphore locks and unlocks to be detected and reported. |
5149cbac4 locking/rwsem: Ad... |
1284 |
|
4d9f34ad3 [PATCH] lockdep: ... |
1285 1286 |
config DEBUG_LOCK_ALLOC bool "Lock debugging: detect incorrect freeing of live locks" |
f07cbebb6 locking/Kconfig: ... |
1287 |
depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
4d9f34ad3 [PATCH] lockdep: ... |
1288 |
select DEBUG_SPINLOCK |
bb630f9f7 locking/rtmutex: ... |
1289 |
select DEBUG_MUTEXES if !PREEMPT_RT |
f5694788a rt_mutex: Add loc... |
1290 |
select DEBUG_RT_MUTEXES if RT_MUTEXES |
4d9f34ad3 [PATCH] lockdep: ... |
1291 1292 1293 1294 1295 1296 1297 1298 |
select LOCKDEP help This feature will check whether any held lock (spinlock, rwlock, mutex or rwsem) is incorrectly freed by the kernel, via any of the memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), vfree(), etc.), whether a live lock is incorrectly reinitialized via spin_lock_init()/mutex_init()/etc., or whether there is any lock held during task exit. |
4d9f34ad3 [PATCH] lockdep: ... |
1299 1300 |
config LOCKDEP bool |
f07cbebb6 locking/Kconfig: ... |
1301 |
depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT |
4d9f34ad3 [PATCH] lockdep: ... |
1302 |
select STACKTRACE |
4d9f34ad3 [PATCH] lockdep: ... |
1303 1304 |
select KALLSYMS select KALLSYMS_ALL |
395102db4 sparc64: Use LOCK... |
1305 1306 |
config LOCKDEP_SMALL bool |
5dc33592e lockdep: Allow tu... |
1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 |
config LOCKDEP_BITS int "Bitsize for MAX_LOCKDEP_ENTRIES" depends on LOCKDEP && !LOCKDEP_SMALL range 10 30 default 15 help Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message. config LOCKDEP_CHAINS_BITS int "Bitsize for MAX_LOCKDEP_CHAINS" depends on LOCKDEP && !LOCKDEP_SMALL range 10 30 default 16 help Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message. config LOCKDEP_STACK_TRACE_BITS int "Bitsize for MAX_STACK_TRACE_ENTRIES" depends on LOCKDEP && !LOCKDEP_SMALL range 10 30 default 19 help Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message. config LOCKDEP_STACK_TRACE_HASH_BITS int "Bitsize for STACK_TRACE_HASH_SIZE" depends on LOCKDEP && !LOCKDEP_SMALL range 10 30 default 14 help Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES. config LOCKDEP_CIRCULAR_QUEUE_BITS int "Bitsize for elements in circular_queue struct" depends on LOCKDEP range 10 30 default 12 help Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure. |
4d9f34ad3 [PATCH] lockdep: ... |
1346 1347 |
config DEBUG_LOCKDEP bool "Lock dependency engine debugging" |
517e7aa5b [PATCH] let the t... |
1348 |
depends on DEBUG_KERNEL && LOCKDEP |
997acaf6b lockdep: report b... |
1349 |
select DEBUG_IRQFLAGS |
4d9f34ad3 [PATCH] lockdep: ... |
1350 1351 1352 1353 |
help If you say Y here, the lock dependency engine will do additional runtime checks to debug itself, at the price of more runtime overhead. |
d902db1eb sched: Generalize... |
1354 1355 |
config DEBUG_ATOMIC_SLEEP bool "Sleep inside atomic section checking" |
e8f7c70f4 sched: Make sleep... |
1356 |
select PREEMPT_COUNT |
1da177e4c Linux-2.6.12-rc2 |
1357 |
depends on DEBUG_KERNEL |
87a4c3759 kconfig: include ... |
1358 |
depends on !ARCH_NO_PREEMPT |
1da177e4c Linux-2.6.12-rc2 |
1359 1360 |
help If you say Y here, various routines which may sleep will become very |
d902db1eb sched: Generalize... |
1361 1362 1363 |
noisy if they are called inside atomic sections: when a spinlock is held, inside an rcu read side critical section, inside preempt disabled sections, inside an interrupt, etc... |
1da177e4c Linux-2.6.12-rc2 |
1364 |
|
cae2ed9aa [PATCH] lockdep: ... |
1365 1366 1367 1368 1369 1370 1371 |
config DEBUG_LOCKING_API_SELFTESTS bool "Locking API boot-time self-tests" depends on DEBUG_KERNEL help Say Y here if you want the kernel to run a short self-test during bootup. The self-test checks whether common types of locking bugs are detected by debugging mechanisms or not. (if you disable |
9dbbc3b9d lib: fix spelling... |
1372 |
lock debugging then those bugs won't be detected of course.) |
cae2ed9aa [PATCH] lockdep: ... |
1373 1374 |
The following locking APIs are covered: spinlocks, rwlocks, mutexes and rwsems. |
0af3fe1ef locktorture: Add ... |
1375 1376 1377 1378 |
config LOCK_TORTURE_TEST tristate "torture tests for locking" depends on DEBUG_KERNEL select TORTURE_TEST |
0af3fe1ef locktorture: Add ... |
1379 1380 1381 1382 1383 1384 1385 1386 1387 |
help This option provides a kernel module that runs torture tests on kernel locking primitives. The kernel module may be built after the fact on the running kernel to be tested, if desired. Say Y here if you want kernel locking-primitive torture tests to be built into the kernel. Say M if you want these torture tests to build as a module. Say N if you are unsure. |
f2a5fec17 locking/ww_mutex:... |
1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 |
config WW_MUTEX_SELFTEST tristate "Wait/wound mutex selftests" help This option provides a kernel module that runs tests on the on the struct ww_mutex locking API. It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction with this test harness. Say M if you want these self tests to build as a module. Say N if you are unsure. |
e9d338a0b scftorture: Add s... |
1399 1400 1401 1402 1403 1404 1405 1406 1407 |
config SCF_TORTURE_TEST tristate "torture tests for smp_call_function*()" depends on DEBUG_KERNEL select TORTURE_TEST help This option provides a kernel module that runs torture tests on the smp_call_function() family of primitives. The kernel module may be built after the fact on the running kernel to be tested, if desired. |
35feb6047 kernel/smp: Provi... |
1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 |
config CSD_LOCK_WAIT_DEBUG bool "Debugging for csd_lock_wait(), called from smp_call_function*()" depends on DEBUG_KERNEL depends on 64BIT default n help This option enables debug prints when CPUs are slow to respond to the smp_call_function*() IPI wrappers. These debug prints include the IPI handler function currently executing (if any) and relevant stack traces. |
9eade16b4 group locking deb... |
1418 |
endmenu # lock debugging |
8637c0990 [PATCH] lockdep: ... |
1419 |
|
9eade16b4 group locking deb... |
1420 |
config TRACE_IRQFLAGS |
ed0049533 locking/lockdep: ... |
1421 |
depends on TRACE_IRQFLAGS_SUPPORT |
9eade16b4 group locking deb... |
1422 |
bool |
5ca43f6c3 lib: consolidate ... |
1423 |
help |
9eade16b4 group locking deb... |
1424 1425 |
Enables hooks to interrupt enabling and disabling for either tracing or lock debugging. |
5ca43f6c3 lib: consolidate ... |
1426 |
|
ed0049533 locking/lockdep: ... |
1427 1428 1429 1430 |
config TRACE_IRQFLAGS_NMI def_bool y depends on TRACE_IRQFLAGS depends on TRACE_IRQFLAGS_NMI_SUPPORT |
997acaf6b lockdep: report b... |
1431 1432 1433 1434 1435 1436 |
config DEBUG_IRQFLAGS bool "Debug IRQ flag manipulation" help Enables checks for potentially unsafe enabling or disabling of interrupts, such as calling raw_local_irq_restore() when interrupts are enabled. |
8637c0990 [PATCH] lockdep: ... |
1437 |
config STACKTRACE |
0c38e1fe0 lib: turn CONFIG_... |
1438 |
bool "Stack backtrace support" |
8637c0990 [PATCH] lockdep: ... |
1439 |
depends on STACKTRACE_SUPPORT |
0c38e1fe0 lib: turn CONFIG_... |
1440 1441 1442 1443 1444 |
help This option causes the kernel to create a /proc/pid/stack for every process, showing its current stack trace. It is also used by various kernel debugging features that require stack trace generation. |
5ca43f6c3 lib: consolidate ... |
1445 |
|
eecabf567 random: suppress ... |
1446 1447 1448 |
config WARN_ALL_UNSEEDED_RANDOM bool "Warn for all uses of unseeded randomness" default n |
d06bfd198 random: warn when... |
1449 1450 1451 1452 1453 1454 1455 1456 |
help Some parts of the kernel contain bugs relating to their use of cryptographically secure random numbers before it's actually possible to generate those numbers securely. This setting ensures that these flaws don't go unnoticed, by enabling a message, should this ever occur. This will allow people with obscure setups to know when things are going wrong, so that they might contact developers about fixing it. |
eecabf567 random: suppress ... |
1457 1458 1459 1460 1461 1462 |
Unfortunately, on some models of some architectures getting a fully seeded CRNG is extremely difficult, and so this can result in dmesg getting spammed for a surprisingly long time. This is really bad from a security perspective, and so architecture maintainers really need to do what they can to get the CRNG seeded sooner after the system is booted. |
4c5d114ea lib/Kconfig.debug... |
1463 |
However, since users cannot do anything actionable to |
8df752b82 random: remove ra... |
1464 |
address this, by default this option is disabled. |
eecabf567 random: suppress ... |
1465 1466 1467 |
Say Y here if you want to receive warnings for all uses of unseeded randomness. This will be of use primarily for |
4c5d114ea lib/Kconfig.debug... |
1468 |
those developers interested in improving the security of |
eecabf567 random: suppress ... |
1469 1470 |
Linux kernels running on their architecture (or subarchitecture). |
d06bfd198 random: warn when... |
1471 |
|
1da177e4c Linux-2.6.12-rc2 |
1472 1473 1474 1475 1476 |
config DEBUG_KOBJECT bool "kobject debugging" depends on DEBUG_KERNEL help If you say Y here, some extra kobject debugging messages will be sent |
aca52c398 mm: remove CONFIG... |
1477 |
to the syslog. |
1da177e4c Linux-2.6.12-rc2 |
1478 |
|
c817a67ec kobject: delayed ... |
1479 1480 |
config DEBUG_KOBJECT_RELEASE bool "kobject release debugging" |
2a999aa0a Kconfig: make KOB... |
1481 |
depends on DEBUG_OBJECTS_TIMERS |
c817a67ec kobject: delayed ... |
1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 |
help kobjects are reference counted objects. This means that their last reference count put is not predictable, and the kobject can live on past the point at which a driver decides to drop it's initial reference to the kobject gained on allocation. An example of this would be a struct device which has just been unregistered. However, some buggy drivers assume that after such an operation, the memory backing the kobject can be immediately freed. This goes completely against the principles of a refcounted object. If you say Y here, the kernel will delay the release of kobjects on the last reference count to improve the visibility of this kind of kobject release bug. |
9b2a60c48 Kconfig: clean up... |
1497 1498 |
config HAVE_DEBUG_BUGVERBOSE bool |
3be5cbcde kernel-hacking: g... |
1499 |
menu "Debug kernel data structures" |
1da177e4c Linux-2.6.12-rc2 |
1500 |
|
199a9afc3 [PATCH] Debug var... |
1501 1502 |
config DEBUG_LIST bool "Debug linked list manipulation" |
4520bcb2b bug: Avoid Kconfi... |
1503 |
depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION |
199a9afc3 [PATCH] Debug var... |
1504 1505 1506 1507 1508 |
help Enable this to turn on extended checks in the linked-list walking routines. If unsure, say N. |
8e18faeac lib/plist: rename... |
1509 |
config DEBUG_PLIST |
b8cfff68e lib/plist.c: make... |
1510 1511 1512 1513 1514 1515 1516 1517 |
bool "Debug priority linked list manipulation" depends on DEBUG_KERNEL help Enable this to turn on extended checks in the priority-ordered linked-list (plist) walking routines. This checks the entire list multiple times during each manipulation. If unsure, say N. |
d6ec08420 Add CONFIG_DEBUG_... |
1518 1519 1520 1521 1522 1523 1524 1525 1526 |
config DEBUG_SG bool "Debug SG table operations" depends on DEBUG_KERNEL help Enable this to turn on checks on scatter-gather tables. This can help find problems with drivers that do not properly initialize their sg tables. If unsure, say N. |
1b2439dbb debug: add notifi... |
1527 1528 1529 1530 1531 1532 1533 1534 1535 |
config DEBUG_NOTIFIERS bool "Debug notifier call chains" depends on DEBUG_KERNEL help Enable this to turn on sanity checking for notifier call chains. This is most useful for kernel developers to make sure that modules properly unregister themselves from notifier chains. This is a relatively cheap check but if you care about maximum performance, say N. |
3be5cbcde kernel-hacking: g... |
1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 |
config BUG_ON_DATA_CORRUPTION bool "Trigger a BUG when data corruption is detected" select DEBUG_LIST help Select this option if the kernel should BUG when it encounters data corruption in kernel memory structures when they get checked for validity. If unsure, say N. endmenu |
e0e817392 CRED: Add some co... |
1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 |
config DEBUG_CREDENTIALS bool "Debug credential management" depends on DEBUG_KERNEL help Enable this to turn on some debug checking for credential management. The additional code keeps track of the number of pointers from task_structs to any given cred struct, and checks to see that this number never exceeds the usage count of the cred struct. Furthermore, if SELinux is enabled, this also checks that the security pointer in the cred struct is never seen to be invalid. If unsure, say N. |
43a0a2a7d rcu: Move RCU deb... |
1561 |
source "kernel/rcu/Kconfig.debug" |
2f03e3ca7 rcu: Consolidate ... |
1562 |
|
f303fccb8 workqueue: implem... |
1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 |
config DEBUG_WQ_FORCE_RR_CPU bool "Force round-robin CPU selection for unbound work items" depends on DEBUG_KERNEL default n help Workqueue used to implicitly guarantee that work items queued without explicit CPU specified are put on the local CPU. This guarantee is no longer true and while local CPU is still preferred work items may be put on foreign CPUs. Kernel parameter "workqueue.debug_force_rr_cpu" is added to force round-robin CPU selection to flush out usages which depend on the now broken guarantee. This config option enables the debug feature by default. When enabled, memory and cache locality will be impacted. |
757c989b9 cpu/hotplug: Make... |
1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 |
config CPU_HOTPLUG_STATE_CONTROL bool "Enable CPU hotplug state control" depends on DEBUG_KERNEL depends on HOTPLUG_CPU default n help Allows to write steps between "offline" and "online" to the CPUs sysfs target file so states can be stepped granular. This is a debug option for now as the hotplug machinery cannot be stopped and restarted at arbitrary points yet. Say N if your are unsure. |
09a749525 kernel-hacking: m... |
1589 1590 1591 1592 1593 |
config LATENCYTOP bool "Latency measuring infrastructure" depends on DEBUG_KERNEL depends on STACKTRACE_SUPPORT depends on PROC_FS |
7d37cb2c9 lib: fix kconfig ... |
1594 |
depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86 |
09a749525 kernel-hacking: m... |
1595 1596 1597 1598 |
select KALLSYMS select KALLSYMS_ALL select STACKTRACE select SCHEDSTATS |
09a749525 kernel-hacking: m... |
1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 |
help Enable this option if you want to use the LatencyTOP tool to find out which userspace is blocking on what kernel operations. source "kernel/trace/Kconfig" config PROVIDE_OHCI1394_DMA_INIT bool "Remote debugging over FireWire early on boot" depends on PCI && X86 help If you want to debug problems which hang or crash the kernel early on boot and the crashing machine has a FireWire port, you can use this feature to remotely access the memory of the crashed machine over FireWire. This employs remote DMA as part of the OHCI1394 specification which is now the standard for FireWire controllers. With remote DMA, you can monitor the printk buffer remotely using firescope and access all memory below 4GB using fireproxy from gdb. Even controlling a kernel debugger is possible using remote DMA. Usage: If ohci1394_dma=early is used as boot parameter, it will initialize all OHCI1394 controllers which are found in the PCI config space. As all changes to the FireWire bus such as enabling and disabling devices cause a bus reset and thereby disable remote DMA for all devices, be sure to have the cable plugged and FireWire enabled on the debugging host before booting the debug target for debugging. This code (~1k) is freed after boot. By then, the firewire stack in charge of the OHCI-1394 controllers should be used instead. |
a74e2a226 docs: debugging-v... |
1631 |
See Documentation/core-api/debugging-via-ohci1394.rst for more information. |
09a749525 kernel-hacking: m... |
1632 |
|
045f6d794 lib/Kconfig.debug... |
1633 1634 1635 1636 1637 1638 1639 1640 |
source "samples/Kconfig" config ARCH_HAS_DEVMEM_IS_ALLOWED bool config STRICT_DEVMEM bool "Filter access to /dev/mem" depends on MMU && DEVMEM |
527701eda lib: Add a generi... |
1641 |
depends on ARCH_HAS_DEVMEM_IS_ALLOWED || GENERIC_LIB_DEVMEM_IS_ALLOWED |
045f6d794 lib/Kconfig.debug... |
1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 |
default y if PPC || X86 || ARM64 help If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel. Note that with PAT support enabled, even in this case there are restrictions on /dev/mem use due to the cache aliasing requirements. If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem file only allows userspace access to PCI space and the BIOS code and data regions. This is sufficient for dosemu and X and all common users of /dev/mem. If in doubt, say Y. config IO_STRICT_DEVMEM bool "Filter I/O access to /dev/mem" depends on STRICT_DEVMEM help If this option is disabled, you allow userspace (root) access to all io-memory regardless of whether a driver is actively using that range. Accidental access to this is obviously disastrous, but specific access can be used by people debugging kernel drivers. If this option is switched on, the /dev/mem file only allows userspace access to *idle* io-memory ranges (see /proc/iomem) This may break traditional users of /dev/mem (dosemu, legacy X, etc...) if the driver using a given range cannot be disabled. If in doubt, say Y. menu "$(SRCARCH) Debugging" source "arch/$(SRCARCH)/Kconfig.debug" endmenu menu "Kernel Testing and Coverage" |
09a749525 kernel-hacking: m... |
1681 |
source "lib/kunit/Kconfig" |
8d4382881 fault-injection: ... |
1682 1683 1684 1685 1686 |
config NOTIFIER_ERROR_INJECTION tristate "Notifier error injection" depends on DEBUG_KERNEL select DEBUG_FS help |
e41e85cc1 treewide: Fix typ... |
1687 |
This option provides the ability to inject artificial errors to |
8d4382881 fault-injection: ... |
1688 1689 1690 1691 |
specified notifier chain callbacks. It is useful to test the error handling of notifier call chain failures. Say N if unsure. |
048b9c354 PM: PM notifier e... |
1692 1693 1694 1695 1696 |
config PM_NOTIFIER_ERROR_INJECT tristate "PM notifier error injection module" depends on PM && NOTIFIER_ERROR_INJECTION default m if PM_DEBUG help |
e41e85cc1 treewide: Fix typ... |
1697 |
This option provides the ability to inject artificial errors to |
048b9c354 PM: PM notifier e... |
1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 |
PM notifier chain callbacks. It is controlled through debugfs interface /sys/kernel/debug/notifier-error-inject/pm If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject PM suspend error (-12 = -ENOMEM) # cd /sys/kernel/debug/notifier-error-inject/pm/ # echo -12 > actions/PM_SUSPEND_PREPARE/error # echo mem > /sys/power/state bash: echo: write error: Cannot allocate memory To compile this code as a module, choose M here: the module will be called pm-notifier-error-inject. If unsure, say N. |
d526e85f6 powerpc+of: Renam... |
1715 1716 1717 |
config OF_RECONFIG_NOTIFIER_ERROR_INJECT tristate "OF reconfig notifier error injection module" depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION |
08dfb4dde powerpc: pSeries ... |
1718 |
help |
e41e85cc1 treewide: Fix typ... |
1719 |
This option provides the ability to inject artificial errors to |
d526e85f6 powerpc+of: Renam... |
1720 |
OF reconfig notifier chain callbacks. It is controlled |
08dfb4dde powerpc: pSeries ... |
1721 |
through debugfs interface under |
d526e85f6 powerpc+of: Renam... |
1722 |
/sys/kernel/debug/notifier-error-inject/OF-reconfig/ |
08dfb4dde powerpc: pSeries ... |
1723 1724 1725 1726 1727 |
If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". To compile this code as a module, choose M here: the module will |
e12a95f40 notifier-error-in... |
1728 |
be called of-reconfig-notifier-error-inject. |
08dfb4dde powerpc: pSeries ... |
1729 1730 |
If unsure, say N. |
02fff96a7 net: add support ... |
1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 |
config NETDEV_NOTIFIER_ERROR_INJECT tristate "Netdev notifier error injection module" depends on NET && NOTIFIER_ERROR_INJECTION help This option provides the ability to inject artificial errors to netdevice notifier chain callbacks. It is controlled through debugfs interface /sys/kernel/debug/notifier-error-inject/netdev If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject netdevice mtu change error (-22 = -EINVAL) # cd /sys/kernel/debug/notifier-error-inject/netdev # echo -22 > actions/NETDEV_CHANGEMTU/error # ip link set eth0 mtu 1024 RTNETLINK answers: Invalid argument To compile this code as a module, choose M here: the module will be called netdev-notifier-error-inject. If unsure, say N. |
f1b4bd067 fault-injection: ... |
1753 1754 1755 |
config FUNCTION_ERROR_INJECTION def_bool y depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES |
6ff1cb355 [PATCH] fault-inj... |
1756 |
config FAULT_INJECTION |
1ab8509a3 [PATCH] fault-inj... |
1757 1758 |
bool "Fault-injection framework" depends on DEBUG_KERNEL |
329409aed [PATCH] fault inj... |
1759 1760 1761 |
help Provide fault-injection framework. For more details, see Documentation/fault-injection/. |
6ff1cb355 [PATCH] fault-inj... |
1762 |
|
8a8b6502f [PATCH] fault-inj... |
1763 |
config FAILSLAB |
1ab8509a3 [PATCH] fault-inj... |
1764 1765 |
bool "Fault-injection capability for kmalloc" depends on FAULT_INJECTION |
773ff60e8 SLUB: failslab su... |
1766 |
depends on SLAB || SLUB |
8a8b6502f [PATCH] fault-inj... |
1767 |
help |
1ab8509a3 [PATCH] fault-inj... |
1768 |
Provide fault-injection capability for kmalloc. |
8a8b6502f [PATCH] fault-inj... |
1769 |
|
933e312e7 [PATCH] fault-inj... |
1770 |
config FAIL_PAGE_ALLOC |
29b46fa3d lib/Kconfig.debug... |
1771 |
bool "Fault-injection capability for alloc_pages()" |
1ab8509a3 [PATCH] fault-inj... |
1772 |
depends on FAULT_INJECTION |
933e312e7 [PATCH] fault-inj... |
1773 |
help |
1ab8509a3 [PATCH] fault-inj... |
1774 |
Provide fault-injection capability for alloc_pages(). |
933e312e7 [PATCH] fault-inj... |
1775 |
|
2c739ced5 lib, include/linu... |
1776 1777 1778 1779 1780 1781 |
config FAULT_INJECTION_USERCOPY bool "Fault injection capability for usercopy functions" depends on FAULT_INJECTION help Provides fault-injection capability to inject failures in usercopy functions (copy_from_user(), get_user(), ...). |
c17bb4951 [PATCH] fault-inj... |
1782 |
config FAIL_MAKE_REQUEST |
86327d19f Fix typo in new d... |
1783 |
bool "Fault-injection capability for disk IO" |
581d4e28d block: add fault ... |
1784 |
depends on FAULT_INJECTION && BLOCK |
c17bb4951 [PATCH] fault-inj... |
1785 |
help |
1ab8509a3 [PATCH] fault-inj... |
1786 |
Provide fault-injection capability for disk IO. |
c17bb4951 [PATCH] fault-inj... |
1787 |
|
581d4e28d block: add fault ... |
1788 |
config FAIL_IO_TIMEOUT |
f4d014395 Kconfig.debug: FA... |
1789 |
bool "Fault-injection capability for faking disk interrupts" |
581d4e28d block: add fault ... |
1790 1791 1792 1793 1794 1795 1796 |
depends on FAULT_INJECTION && BLOCK help Provide fault-injection capability on end IO handling. This will make the block layer "forget" an interrupt as configured, thus exercising the error handling. Only works with drivers that use the generic timeout handling, |
9dbbc3b9d lib: fix spelling... |
1797 |
for others it won't do anything. |
581d4e28d block: add fault ... |
1798 |
|
ab51fbab3 futex: Fault/erro... |
1799 1800 1801 1802 1803 1804 |
config FAIL_FUTEX bool "Fault-injection capability for futexes" select DEBUG_FS depends on FAULT_INJECTION && FUTEX help Provide fault-injection capability for futexes. |
f1b4bd067 fault-injection: ... |
1805 1806 1807 1808 1809 |
config FAULT_INJECTION_DEBUG_FS bool "Debugfs entries for fault-injection capabilities" depends on FAULT_INJECTION && SYSFS && DEBUG_FS help Enable configuration of fault-injection capabilities via debugfs. |
4b1a29a7f error-injection: ... |
1810 1811 1812 1813 1814 1815 1816 1817 1818 |
config FAIL_FUNCTION bool "Fault-injection capability for functions" depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION help Provide function-based fault-injection capability. This will allow you to override a specific function with a return with given return value. As a result, function caller will see an error value and have to handle it. This is useful to test the error handling in various subsystems. |
f1b4bd067 fault-injection: ... |
1819 1820 1821 |
config FAIL_MMC_REQUEST bool "Fault-injection capability for MMC IO" depends on FAULT_INJECTION_DEBUG_FS && MMC |
6ff1cb355 [PATCH] fault-inj... |
1822 |
help |
f1b4bd067 fault-injection: ... |
1823 1824 1825 1826 1827 |
Provide fault-injection capability for MMC IO. This will make the mmc core return data errors. This is useful to test the error handling in the mmc block device and to test how the mmc host driver handles retries from the block device. |
1df49008f [PATCH] fault inj... |
1828 |
|
c782af250 SUNRPC: Add a /sy... |
1829 1830 1831 1832 1833 1834 |
config FAIL_SUNRPC bool "Fault-injection capability for SunRPC" depends on FAULT_INJECTION_DEBUG_FS && SUNRPC_DEBUG help Provide fault-injection capability for SunRPC and its consumers. |
1df49008f [PATCH] fault inj... |
1835 1836 1837 |
config FAULT_INJECTION_STACKTRACE_FILTER bool "stacktrace filter for fault-injection capabilities" depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT |
6d690dcac fault injection: ... |
1838 |
depends on !X86_64 |
1df49008f [PATCH] fault inj... |
1839 |
select STACKTRACE |
7d37cb2c9 lib: fix kconfig ... |
1840 |
depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86 |
1df49008f [PATCH] fault inj... |
1841 1842 |
help Provide stacktrace filter for fault-injection capabilities |
267c4025f markers: Add samp... |
1843 |
|
09a749525 kernel-hacking: m... |
1844 1845 |
config ARCH_HAS_KCOV bool |
cc3fa8404 lib/Kconfig.debug... |
1846 |
help |
09a749525 kernel-hacking: m... |
1847 1848 1849 |
An architecture should select this when it can successfully build and run with CONFIG_KCOV. This typically requires disabling instrumentation for some early boot code. |
cc3fa8404 lib/Kconfig.debug... |
1850 |
|
09a749525 kernel-hacking: m... |
1851 1852 |
config CC_HAS_SANCOV_TRACE_PC def_bool $(cc-option,-fsanitize-coverage=trace-pc) |
cc3fa8404 lib/Kconfig.debug... |
1853 |
|
cc3fa8404 lib/Kconfig.debug... |
1854 |
|
09a749525 kernel-hacking: m... |
1855 1856 1857 1858 1859 1860 1861 1862 1863 |
config KCOV bool "Code coverage for fuzzing" depends on ARCH_HAS_KCOV depends on CC_HAS_SANCOV_TRACE_PC || GCC_PLUGINS select DEBUG_FS select GCC_PLUGIN_SANCOV if !CC_HAS_SANCOV_TRACE_PC help KCOV exposes kernel code coverage information in a form suitable for coverage-guided fuzzing (randomized testing). |
cc3fa8404 lib/Kconfig.debug... |
1864 |
|
09a749525 kernel-hacking: m... |
1865 1866 1867 |
If RANDOMIZE_BASE is enabled, PC values will not be stable across different machines and across reboots. If you need stable PC values, disable RANDOMIZE_BASE. |
cc3fa8404 lib/Kconfig.debug... |
1868 |
|
09a749525 kernel-hacking: m... |
1869 |
For more details, see Documentation/dev-tools/kcov.rst. |
cc3fa8404 lib/Kconfig.debug... |
1870 |
|
09a749525 kernel-hacking: m... |
1871 1872 1873 1874 1875 1876 1877 1878 1879 |
config KCOV_ENABLE_COMPARISONS bool "Enable comparison operands collection by KCOV" depends on KCOV depends on $(cc-option,-fsanitize-coverage=trace-cmp) help KCOV also exposes operands of every comparison in the instrumented code along with operand sizes and PCs of the comparison instructions. These operands can be used by fuzzing engines to improve the quality of fuzzing coverage. |
cc3fa8404 lib/Kconfig.debug... |
1880 |
|
09a749525 kernel-hacking: m... |
1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 |
config KCOV_INSTRUMENT_ALL bool "Instrument all code by default" depends on KCOV default y help If you are doing generic system call fuzzing (like e.g. syzkaller), then you will want to instrument the whole kernel and you should say y here. If you are doing more targeted fuzzing (like e.g. filesystem fuzzing with AFL) then you will want to enable coverage for more specific subsets of files, and should say n here. |
84bc809ee lib: enable build... |
1891 |
|
5ff3b30ab kcov: collect cov... |
1892 1893 1894 1895 1896 1897 1898 1899 |
config KCOV_IRQ_AREA_SIZE hex "Size of interrupt coverage collection area in words" depends on KCOV default 0x40000 help KCOV uses preallocated per-cpu areas to collect coverage from soft interrupts. This specifies the size of those areas in the number of unsigned long words. |
d3deafaa8 lib/: make RUNTIM... |
1900 1901 |
menuconfig RUNTIME_TESTING_MENU bool "Runtime Testing" |
908009e83 lib/Kconfig.debug... |
1902 |
def_bool y |
d3deafaa8 lib/: make RUNTIM... |
1903 1904 |
if RUNTIME_TESTING_MENU |
881c51495 consolidate runti... |
1905 1906 1907 1908 |
config LKDTM tristate "Linux Kernel Dump Test Tool Module" depends on DEBUG_FS |
881c51495 consolidate runti... |
1909 1910 1911 1912 1913 1914 1915 1916 |
help This module enables testing of the different dumping mechanisms by inducing system failures at predefined crash points. If you don't need it: say N Choose M here to compile this code as a module. The module will be called lkdtm. Documentation on how to use the module can be found in |
10ffebbed docs: fault-injec... |
1917 |
Documentation/fault-injection/provoke-crashes.rst |
881c51495 consolidate runti... |
1918 1919 |
config TEST_LIST_SORT |
ebd09577b lib/test: convert... |
1920 1921 1922 |
tristate "Linked list sorting test" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS |
881c51495 consolidate runti... |
1923 1924 |
help Enable this to turn on 'list_sort()' function test. This test is |
e327fd7c8 lib: add module s... |
1925 1926 |
executed only once during system boot (so affects only boot time), or at module load time. |
881c51495 consolidate runti... |
1927 1928 |
If unsure, say N. |
6e24628d7 lib: Introduce ge... |
1929 1930 1931 1932 1933 1934 1935 1936 1937 |
config TEST_MIN_HEAP tristate "Min heap test" depends on DEBUG_KERNEL || m help Enable this to turn on min heap function tests. This test is executed only once during system boot (so affects only boot time), or at module load time. If unsure, say N. |
c5adae958 lib: add CONFIG_T... |
1938 |
config TEST_SORT |
36f33b562 lib/test: convert... |
1939 1940 1941 |
tristate "Array-based sort test" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS |
c5adae958 lib: add CONFIG_T... |
1942 |
help |
5c4e67989 lib: add module s... |
1943 1944 |
This option enables the self-test function of 'sort()' at boot, or at module load time. |
c5adae958 lib: add CONFIG_T... |
1945 1946 |
If unsure, say N. |
5086ea4b0 lib/math: Add a `... |
1947 1948 1949 1950 1951 1952 1953 1954 1955 |
config TEST_DIV64 tristate "64bit/32bit division and modulo test" depends on DEBUG_KERNEL || m help Enable this to turn on 'do_div()' function test. This test is executed only once during system boot (so affects only boot time), or at module load time. If unsure, say N. |
881c51495 consolidate runti... |
1956 1957 1958 1959 |
config KPROBES_SANITY_TEST bool "Kprobes sanity tests" depends on DEBUG_KERNEL depends on KPROBES |
881c51495 consolidate runti... |
1960 1961 |
help This option provides for testing basic kprobes functionality on |
5a6cf77f5 kprobes: Remove j... |
1962 |
boot. Samples of kprobe and kretprobe are inserted and |
881c51495 consolidate runti... |
1963 1964 1965 1966 1967 1968 1969 |
verified for functionality. Say N if you are unsure. config BACKTRACE_SELF_TEST tristate "Self test for the backtrace code" depends on DEBUG_KERNEL |
881c51495 consolidate runti... |
1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 |
help This option provides a kernel module that can be used to test the kernel stack backtrace code. This option is not useful for distributions or general kernels, but only for kernel developers working on architecture code. Note that if you want to also test saved backtraces, you will have to enable STACKTRACE as well. Say N if you are unsure. |
910a742d4 rbtree: performan... |
1980 1981 |
config RBTREE_TEST tristate "Red-Black tree test" |
7c993e11a rbtree: allow tes... |
1982 |
depends on DEBUG_KERNEL |
910a742d4 rbtree: performan... |
1983 1984 1985 |
help A benchmark measuring the performance of the rbtree library. Also includes rbtree invariant checks. |
4b4f3accd rslib: Add tests ... |
1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 |
config REED_SOLOMON_TEST tristate "Reed-Solomon library test" depends on DEBUG_KERNEL || m select REED_SOLOMON select REED_SOLOMON_ENC16 select REED_SOLOMON_DEC16 help This option enables the self-test function of rslib at boot, or at module load time. If unsure, say N. |
fff3fd8a1 rbtree: add prio ... |
1997 1998 |
config INTERVAL_TREE_TEST tristate "Interval tree test" |
0f789b676 lib/interval_tree... |
1999 |
depends on DEBUG_KERNEL |
a88cc108f lib: Export inter... |
2000 |
select INTERVAL_TREE |
fff3fd8a1 rbtree: add prio ... |
2001 2002 |
help A benchmark measuring the performance of the interval tree library |
623fd8072 percpu: add test ... |
2003 2004 2005 2006 2007 2008 2009 2010 |
config PERCPU_TEST tristate "Per cpu operations test" depends on m && DEBUG_KERNEL help Enable this option to build test module which validates per-cpu operations. If unsure, say N. |
881c51495 consolidate runti... |
2011 |
config ATOMIC64_SELFTEST |
55ded9551 lib: add module s... |
2012 |
tristate "Perform an atomic64_t self-test" |
881c51495 consolidate runti... |
2013 |
help |
55ded9551 lib: add module s... |
2014 2015 |
Enable this option to test the atomic64_t functions at boot or at module load time. |
881c51495 consolidate runti... |
2016 2017 2018 2019 2020 2021 2022 |
If unsure, say N. config ASYNC_RAID6_TEST tristate "Self test for hardware accelerated raid6 recovery" depends on ASYNC_RAID6_RECOV select ASYNC_MEMCPY |
a7f7f6248 treewide: replace... |
2023 |
help |
881c51495 consolidate runti... |
2024 2025 2026 2027 2028 2029 2030 |
This is a one-shot self test that permutes through the recovery of all the possible two disk failure scenarios for a N-disk array. Recovery is performed with the asynchronous raid6 recovery routines, and will optionally use an offload engine if one is available. If unsure, say N. |
64d1d77a4 hexdump: introduc... |
2031 2032 |
config TEST_HEXDUMP tristate "Test functions located in the hexdump module at runtime" |
b2ff70a01 lib/test_string.c... |
2033 2034 |
config STRING_SELFTEST tristate "Test string functions at runtime" |
881c51495 consolidate runti... |
2035 2036 |
config TEST_STRING_HELPERS tristate "Test functions located in the string_helpers module at runtime" |
0b0600c8c lib: Add test mod... |
2037 2038 |
config TEST_STRSCPY tristate "Test strscpy*() family of functions at runtime" |
881c51495 consolidate runti... |
2039 2040 |
config TEST_KSTRTOX tristate "Test kstrto*() family of functions at runtime" |
707cc7280 test_printf: test... |
2041 2042 |
config TEST_PRINTF tristate "Test printf() family of functions at runtime" |
50f530e17 lib: test_scanf: ... |
2043 2044 |
config TEST_SCANF tristate "Test scanf() family of functions at runtime" |
5fd003f56 test_bitmap: unit... |
2045 2046 |
config TEST_BITMAP tristate "Test bitmap_*() family of functions at runtime" |
5fd003f56 test_bitmap: unit... |
2047 2048 2049 2050 |
help Enable this option to test the bitmap functions at boot. If unsure, say N. |
cfaff0e51 lib/uuid: add a t... |
2051 2052 |
config TEST_UUID tristate "Test functions located in the uuid module at runtime" |
ad3d6c726 xarray: Add XArra... |
2053 2054 |
config TEST_XARRAY tristate "Test the XArray code at runtime" |
455a35a6c lib: add runtime ... |
2055 2056 |
config TEST_OVERFLOW tristate "Test check_*_overflow() functions at runtime" |
7e1e77636 lib: Resizable, S... |
2057 |
config TEST_RHASHTABLE |
9d6dbe1bb rhashtable: Make ... |
2058 |
tristate "Perform selftest on resizable hash table" |
7e1e77636 lib: Resizable, S... |
2059 2060 2061 2062 |
help Enable this option to test the rhashtable functions at boot. If unsure, say N. |
468a94285 <linux/hash.h>: A... |
2063 2064 |
config TEST_HASH tristate "Perform selftest on hash functions" |
468a94285 <linux/hash.h>: A... |
2065 |
help |
2c956a607 siphash: add cryp... |
2066 2067 2068 |
Enable this option to test the kernel's integer (<linux/hash.h>), string (<linux/stringhash.h>), and siphash (<linux/siphash.h>) hash functions on boot (or module load). |
468a94285 <linux/hash.h>: A... |
2069 2070 2071 |
This is intended to help people writing architecture-specific optimized versions. If unsure, say N. |
8ab8ba38d ida: Start new te... |
2072 2073 |
config TEST_IDA tristate "Perform selftest on IDA functions" |
44091d29f lib: Introduce pr... |
2074 2075 |
config TEST_PARMAN tristate "Perform selftest on priority array manager" |
44091d29f lib: Introduce pr... |
2076 2077 2078 2079 2080 2081 |
depends on PARMAN help Enable this option to test priority array manager on boot (or module load). If unsure, say N. |
6aed82de7 genirq/timings: A... |
2082 2083 2084 2085 2086 2087 2088 |
config TEST_IRQ_TIMINGS bool "IRQ timings selftest" depends on IRQ_TIMINGS help Enable this option to test the irq timings code on boot. If unsure, say N. |
8a6f0b47d lib: rename TEST_... |
2089 |
config TEST_LKM |
93e9ef83f test: add minimal... |
2090 |
tristate "Test module loading with 'hello world' module" |
93e9ef83f test: add minimal... |
2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 |
depends on m help This builds the "test_module" module that emits "Hello, world" on printk when loaded. It is designed to be used for basic evaluation of the module loading subsystem (for example when validating module verification). It lacks any extra dependencies, and will not normally be loaded by the system unless explicitly requested by name. If unsure, say N. |
c348c1630 lib: make a test ... |
2101 |
config TEST_BITOPS |
6af132f3a lib: test get_cou... |
2102 |
tristate "Test module for compilation of bitops operations" |
c348c1630 lib: make a test ... |
2103 2104 2105 2106 |
depends on m help This builds the "test_bitops" module that is much like the TEST_LKM module except that it does a basic exercise of the |
6af132f3a lib: test get_cou... |
2107 2108 2109 2110 |
set/clear_bit macros and get_count_order/long to make sure there are no compiler warnings from C=1 sparse checker or -Wextra compilations. It has no dependencies and doesn't run or load unless explicitly requested by name. for example: modprobe test_bitops. |
c348c1630 lib: make a test ... |
2111 2112 |
If unsure, say N. |
3f21a6b7e vmalloc: add test... |
2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 |
config TEST_VMALLOC tristate "Test module for stress/performance analysis of vmalloc allocator" default n depends on MMU depends on m help This builds the "test_vmalloc" module that should be used for stress and performance analysis. So, any new change for vmalloc subsystem can be evaluated from performance and stability point of view. If unsure, say N. |
3e2a4c183 test: check copy_... |
2125 2126 |
config TEST_USER_COPY tristate "Test user/kernel boundary protections" |
3e2a4c183 test: check copy_... |
2127 2128 2129 2130 2131 2132 2133 2134 2135 |
depends on m help This builds the "test_user_copy" module that runs sanity checks on the copy_to/from_user infrastructure, making sure basic user/kernel boundary testing is working. If it fails to load, a regression has been detected in the user/kernel memory boundary protections. If unsure, say N. |
64a8946b4 net: filter: BPF ... |
2136 2137 |
config TEST_BPF tristate "Test BPF filter functionality" |
98920ba69 net: fix test_bpf... |
2138 |
depends on m && NET |
64a8946b4 net: filter: BPF ... |
2139 2140 2141 2142 2143 |
help This builds the "test_bpf" module that runs various test vectors against the BPF interpreter or BPF JIT compiler depending on the current setting. This is in particular useful for BPF JIT compiler development, but also to run regression tests against changes in |
3c731eba4 bpf: mini eBPF li... |
2144 2145 |
the interpreter code. It also enables test stubs for eBPF maps and verifier used by user space verifier testsuite. |
64a8946b4 net: filter: BPF ... |
2146 2147 |
If unsure, say N. |
509e56b37 blackhole_dev: ad... |
2148 2149 2150 2151 2152 2153 2154 2155 |
config TEST_BLACKHOLE_DEV tristate "Test blackhole netdev functionality" depends on m && NET help This builds the "test_blackhole_dev" module that validates the data path through this blackhole netdev. If unsure, say N. |
dceeb3e7f lib/test_find_bit... |
2156 |
config FIND_BIT_BENCHMARK |
4441fca0a lib: test module ... |
2157 |
tristate "Test find_bit functions" |
4441fca0a lib: test module ... |
2158 2159 2160 2161 2162 |
help This builds the "test_find_bit" module that measure find_*_bit() functions performance. If unsure, say N. |
0a8adf584 test: add firmwar... |
2163 2164 |
config TEST_FIRMWARE tristate "Test firmware loading via userspace interface" |
0a8adf584 test: add firmwar... |
2165 2166 2167 2168 2169 2170 2171 2172 2173 |
depends on FW_LOADER help This builds the "test_firmware" module that creates a userspace interface for testing firmware loading. This can be used to control the triggering of firmware loading without needing an actual firmware-using device. The contents can be rechecked by userspace. If unsure, say N. |
9308f2f9e test_sysctl: add ... |
2174 2175 |
config TEST_SYSCTL tristate "sysctl test driver" |
9308f2f9e test_sysctl: add ... |
2176 2177 2178 2179 2180 2181 2182 |
depends on PROC_SYSCTL help This builds the "test_sysctl" module. This driver enables to test the proc sysctl interfaces available to drivers safely without affecting production knobs which might alter system functionality. If unsure, say N. |
d2585f516 lib: kunit: add b... |
2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 |
config BITFIELD_KUNIT tristate "KUnit test bitfield functions at runtime" depends on KUNIT help Enable this option to test the bitfield functions at boot. KUnit tests run during boot and output the results to the debug log in TAP format (http://testanything.org/). Only useful for kernel devs running the KUnit test harness, and not intended for inclusion into a production build. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
5df38ca6a resource: Add tes... |
2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 |
config RESOURCE_KUNIT_TEST tristate "KUnit test for resource API" depends on KUNIT help This builds the resource API unit test. Tests the logic of API provided by resource.c and ioport.h. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
2cb80dbbb kernel/sysctl-tes... |
2208 |
config SYSCTL_KUNIT_TEST |
5f215aab4 lib: Kconfig.debu... |
2209 |
tristate "KUnit test for sysctl" if !KUNIT_ALL_TESTS |
2cb80dbbb kernel/sysctl-tes... |
2210 |
depends on KUNIT |
5f215aab4 lib: Kconfig.debu... |
2211 |
default KUNIT_ALL_TESTS |
2cb80dbbb kernel/sysctl-tes... |
2212 2213 2214 2215 2216 2217 2218 |
help This builds the proc sysctl unit test, which runs on boot. Tests the API contract and implementation correctness of sysctl. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
ea2dd7c08 lib/list-test: ad... |
2219 |
config LIST_KUNIT_TEST |
5f215aab4 lib: Kconfig.debu... |
2220 |
tristate "KUnit Test for Kernel Linked-list structures" if !KUNIT_ALL_TESTS |
ea2dd7c08 lib/list-test: ad... |
2221 |
depends on KUNIT |
5f215aab4 lib: Kconfig.debu... |
2222 |
default KUNIT_ALL_TESTS |
ea2dd7c08 lib/list-test: ad... |
2223 2224 2225 2226 2227 2228 |
help This builds the linked list KUnit test suite. It tests that the API and basic functionality of the list_head type and associated macros. KUnit tests run during boot and output the results to the debug log |
d89775fc9 lib/: replace HTT... |
2229 |
in TAP format (https://testanything.org/). Only useful for kernel devs |
ea2dd7c08 lib/list-test: ad... |
2230 2231 2232 2233 2234 2235 2236 |
running the KUnit test harness, and not intended for inclusion into a production build. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
33d599f05 lib/test_linear_r... |
2237 2238 2239 2240 2241 2242 2243 2244 |
config LINEAR_RANGES_TEST tristate "KUnit test for linear_ranges" depends on KUNIT select LINEAR_RANGES help This builds the linear_ranges unit test, which runs on boot. Tests the linear_ranges logic correctness. For more information on KUnit and unit tests in general please refer |
7546861a8 lib/cmdline_kunit... |
2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 |
to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. config CMDLINE_KUNIT_TEST tristate "KUnit test for cmdline API" depends on KUNIT help This builds the cmdline API unit test. Tests the logic of API provided by cmdline.c. For more information on KUnit and unit tests in general please refer |
33d599f05 lib/test_linear_r... |
2256 2257 2258 |
to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
6d511020e lib/test_bits.c: ... |
2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 |
config BITS_TEST tristate "KUnit test for bits.h" depends on KUNIT help This builds the bits unit test. Tests the logic of macros defined in bits.h. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
1f9f78b1b mm/slub, kunit: a... |
2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 |
config SLUB_KUNIT_TEST tristate "KUnit test for SLUB cache error detection" if !KUNIT_ALL_TESTS depends on SLUB_DEBUG && KUNIT default KUNIT_ALL_TESTS help This builds SLUB allocator unit test. Tests SLUB cache debugging functionality. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
b6c75c4af lib/math/rational... |
2280 2281 |
config RATIONAL_KUNIT_TEST tristate "KUnit test for rational.c" if !KUNIT_ALL_TESTS |
8ba739ede math: RATIONAL_KU... |
2282 |
depends on KUNIT && RATIONAL |
b6c75c4af lib/math/rational... |
2283 2284 2285 2286 2287 2288 2289 |
default KUNIT_ALL_TESTS help This builds the rational math unit test. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. |
e704f93af kernel: time: Add... |
2290 2291 |
config TEST_UDELAY tristate "udelay test driver" |
e704f93af kernel: time: Add... |
2292 2293 2294 2295 2296 |
help This builds the "udelay_test" module that helps to make sure that udelay() is working properly. If unsure, say N. |
2bf9e0ab0 locking/static_ke... |
2297 2298 |
config TEST_STATIC_KEYS tristate "Test static keys" |
579e1acb1 jump_label: Provi... |
2299 2300 |
depends on m help |
2bf9e0ab0 locking/static_ke... |
2301 |
Test the static key interfaces. |
579e1acb1 jump_label: Provi... |
2302 2303 |
If unsure, say N. |
d9c6a72d6 kmod: add test dr... |
2304 2305 |
config TEST_KMOD tristate "kmod stress tester" |
d9c6a72d6 kmod: add test dr... |
2306 |
depends on m |
d9c6a72d6 kmod: add test dr... |
2307 |
depends on NETDEVICES && NET_CORE && INET # for TUN |
ae3d6a323 lib/Kconfig.debug... |
2308 |
depends on BLOCK |
d9c6a72d6 kmod: add test dr... |
2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 |
select TEST_LKM select XFS_FS select TUN select BTRFS_FS help Test the kernel's module loading mechanism: kmod. kmod implements support to load modules using the Linux kernel's usermode helper. This test provides a series of tests against kmod. Although technically you can either build test_kmod as a module or into the kernel we disallow building it into the kernel since it stress tests request_module() and this will very likely cause some issues by taking over precious threads available from other module load requests, ultimately this could be fatal. To run tests run: tools/testing/selftests/kmod/kmod.sh --help If unsure, say N. |
e4dace361 lib: add test mod... |
2329 2330 2331 2332 2333 2334 2335 2336 2337 |
config TEST_DEBUG_VIRTUAL tristate "Test CONFIG_DEBUG_VIRTUAL feature" depends on DEBUG_VIRTUAL help Test the kernel's ability to detect incorrect calls to virt_to_phys() done against the non-linear part of the kernel's virtual address map. If unsure, say N. |
ce76d938d lib: Add memcat_p... |
2338 2339 2340 2341 2342 2343 2344 |
config TEST_MEMCAT_P tristate "Test memcat_p() helper function" help Test the memcat_p() helper for correctly merging two pointer arrays together. If unsure, say N. |
a2818ee4d selftests/livepat... |
2345 2346 2347 |
config TEST_LIVEPATCH tristate "Test livepatching" default n |
bae054372 selftests/livepat... |
2348 |
depends on DYNAMIC_DEBUG |
a2818ee4d selftests/livepat... |
2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 |
depends on LIVEPATCH depends on m help Test kernel livepatching features for correctness. The tests will load test modules that will be livepatched in various scenarios. To run all the livepatching tests: make -C tools/testing/selftests TARGETS=livepatch run_tests Alternatively, individual tests may be invoked: tools/testing/selftests/livepatch/test-callbacks.sh tools/testing/selftests/livepatch/test-livepatch.sh tools/testing/selftests/livepatch/test-shadow-vars.sh If unsure, say N. |
0a020d416 lib: introduce in... |
2366 2367 2368 2369 2370 2371 2372 |
config TEST_OBJAGG tristate "Perform selftest on object aggreration manager" default n depends on OBJAGG help Enable this option to test object aggregation manager on boot (or module load). |
0a020d416 lib: introduce in... |
2373 |
|
50ceaa95e lib: Introduce te... |
2374 2375 2376 2377 2378 2379 2380 2381 2382 |
config TEST_STACKINIT tristate "Test level of stack variable initialization" help Test if the kernel is zero-initializing stack variables and padding. Coverage is controlled by compiler flags, CONFIG_GCC_PLUGIN_STRUCTLEAK, CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF, or CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. If unsure, say N. |
5015a300a lib: introduce te... |
2383 2384 2385 2386 2387 2388 2389 |
config TEST_MEMINIT tristate "Test heap/page initialization" help Test if the kernel is zero-initializing heap and page allocations. This can be useful to test init_on_alloc and init_on_free features. If unsure, say N. |
b2ef9f5a5 mm/hmm/test: add ... |
2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 |
config TEST_HMM tristate "Test HMM (Heterogeneous Memory Management)" depends on TRANSPARENT_HUGEPAGE depends on DEVICE_PRIVATE select HMM_MIRROR select MMU_NOTIFIER help This is a pseudo device driver solely for testing HMM. Say M here if you want to build the HMM test module. Doing so will allow you to run tools/testing/selftest/vm/hmm-tests. If unsure, say N. |
e320d3012 mm/page_alloc.c: ... |
2402 2403 2404 2405 2406 2407 2408 2409 |
config TEST_FREE_PAGES tristate "Test freeing pages" help Test that a memory leak does not occur due to a race between freeing a block of pages and a speculative page reference. Loading this module is safe if your kernel has the bug fixed. If the bug is not fixed, it will leak gigabytes of memory and probably OOM your system. |
4185b3b92 selftests/fpu: Ad... |
2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 |
config TEST_FPU tristate "Test floating point operations in kernel space" depends on X86 && !KCOV_INSTRUMENT_ALL help Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu which will trigger a sequence of floating point operations. This is used for self-testing floating point control register setting in kernel_fpu_begin(). If unsure, say N. |
1253b9b87 clocksource: Prov... |
2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 |
config TEST_CLOCKSOURCE_WATCHDOG tristate "Test clocksource watchdog in kernel space" depends on CLOCKSOURCE_WATCHDOG help Enable this option to create a kernel module that will trigger a test of the clocksource watchdog. This module may be loaded via modprobe or insmod in which case it will run upon being loaded, or it may be built in, in which case it will run shortly after boot. If unsure, say N. |
d3deafaa8 lib/: make RUNTIM... |
2431 |
endif # RUNTIME_TESTING_MENU |
cc3fa8404 lib/Kconfig.debug... |
2432 |
|
dce445661 mm/memtest: add A... |
2433 2434 2435 2436 2437 |
config ARCH_USE_MEMTEST bool help An architecture should select this when it uses early_memtest() during boot process. |
cc3fa8404 lib/Kconfig.debug... |
2438 2439 |
config MEMTEST bool "Memtest" |
dce445661 mm/memtest: add A... |
2440 |
depends on ARCH_USE_MEMTEST |
a7f7f6248 treewide: replace... |
2441 |
help |
cc3fa8404 lib/Kconfig.debug... |
2442 |
This option adds a kernel parameter 'memtest', which allows memtest |
dce445661 mm/memtest: add A... |
2443 |
to be set and executed. |
cc3fa8404 lib/Kconfig.debug... |
2444 2445 2446 2447 2448 |
memtest=0, mean disabled; -- default memtest=1, mean do 1 test pattern; ... memtest=17, mean do 17 test patterns. If you are unsure how to answer this question, answer N. |
21266be9e arch: consolidate... |
2449 |
|
06ec64b84 Kconfig: consolid... |
2450 |
|
af9ca6f9b drivers: hv: vmbu... |
2451 2452 2453 2454 2455 2456 |
config HYPERV_TESTING bool "Microsoft Hyper-V driver testing" default n depends on HYPERV && DEBUG_FS help Select this option to enable Hyper-V vmbus testing. |
045f6d794 lib/Kconfig.debug... |
2457 |
endmenu # "Kernel Testing and Coverage" |
75442fb0c docs: Kconfig/Mak... |
2458 |
source "Documentation/Kconfig" |
06ec64b84 Kconfig: consolid... |
2459 |
endmenu # Kernel hacking |