1 # SPDX-License-Identifier: GPL-2.0-only
4 menu "printk and dmesg options"
7 bool "Show timing information on printks"
10 Selecting this option causes time stamps of the printk()
11 messages to be added to the output of the syslog() system
12 call and at the console.
14 The timestamp is always recorded internally, and exported
15 to /dev/kmsg. This flag just specifies if the timestamp should
16 be included, not that the timestamp is recorded.
18 The behavior is also controlled by the kernel command line
19 parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst
22 bool "Show caller information on printks"
25 Selecting this option causes printk() to add a caller "thread id" (if
26 in task context) or a caller "processor id" (if not in task context)
29 This option is intended for environments where multiple threads
30 concurrently call printk() for many times, for it is difficult to
31 interpret without knowing where these lines (or sometimes individual
32 line which was divided into multiple lines due to race) came from.
34 Since toggling after boot makes the code racy, currently there is
35 no option to enable/disable at the kernel command line parameter or
38 config STACKTRACE_BUILD_ID
39 bool "Show build ID information in stacktraces"
42 Selecting this option adds build ID information for symbols in
43 stacktraces printed with the printk format '%p[SR]b'.
45 This option is intended for distros where debuginfo is not easily
46 accessible but can be downloaded given the build ID of the vmlinux or
47 kernel module where the function is located.
49 config CONSOLE_LOGLEVEL_DEFAULT
50 int "Default console loglevel (1-15)"
54 Default loglevel to determine what will be printed on the console.
56 Setting a default here is equivalent to passing in loglevel=<x> in
57 the kernel bootargs. loglevel=<x> continues to override whatever
58 value is specified here as well.
60 Note: This does not affect the log level of un-prefixed printk()
61 usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT
64 config CONSOLE_LOGLEVEL_QUIET
65 int "quiet console loglevel (1-15)"
69 loglevel to use when "quiet" is passed on the kernel commandline.
71 When "quiet" is passed on the kernel commandline this loglevel
72 will be used as the loglevel. IOW passing "quiet" will be the
73 equivalent of passing "loglevel=<CONSOLE_LOGLEVEL_QUIET>"
75 config MESSAGE_LOGLEVEL_DEFAULT
76 int "Default message log level (1-7)"
80 Default log level for printk statements with no specified priority.
82 This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
83 that are auditing their logs closely may want to set it to a lower
86 Note: This does not affect what message level gets printed on the console
87 by default. To change that, use loglevel=<x> in the kernel bootargs,
88 or pick a different CONSOLE_LOGLEVEL_DEFAULT configuration value.
90 config BOOT_PRINTK_DELAY
91 bool "Delay each boot printk message by N milliseconds"
92 depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY
94 This build option allows you to read kernel boot messages
95 by inserting a short delay after each one. The delay is
96 specified in milliseconds on the kernel command line,
99 It is likely that you would also need to use "lpj=M" to preset
100 the "loops per jiffie" value.
101 See a previous boot log for the "lpj" value to use for your
102 system, and then set "lpj=M" before setting "boot_delay=N".
103 NOTE: Using this option may adversely affect SMP systems.
104 I.e., processors other than the first one may not boot up.
105 BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
106 what it believes to be lockup conditions.
109 bool "Enable dynamic printk() support"
112 depends on (DEBUG_FS || PROC_FS)
113 select DYNAMIC_DEBUG_CORE
116 Compiles debug level messages into the kernel, which would not
117 otherwise be available at runtime. These messages can then be
118 enabled/disabled based on various levels of scope - per source file,
119 function, module, format string, and line number. This mechanism
120 implicitly compiles in all pr_debug() and dev_dbg() calls, which
121 enlarges the kernel text size by about 2%.
123 If a source file is compiled with DEBUG flag set, any
124 pr_debug() calls in it are enabled by default, but can be
125 disabled at runtime as below. Note that DEBUG flag is
126 turned on by many CONFIG_*DEBUG* options.
130 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
131 which is contained in the 'debugfs' filesystem or procfs.
132 Thus, the debugfs or procfs filesystem must first be mounted before
133 making use of this feature.
134 We refer the control file as: <debugfs>/dynamic_debug/control. This
135 file contains a list of the debug statements that can be enabled. The
136 format for each line of the file is:
138 filename:lineno [module]function flags format
140 filename : source file of the debug statement
141 lineno : line number of the debug statement
142 module : module that contains the debug statement
143 function : function that contains the debug statement
144 flags : '=p' means the line is turned 'on' for printing
145 format : the format used for the debug statement
149 nullarbor:~ # cat <debugfs>/dynamic_debug/control
150 # filename:lineno [module]function flags format
151 fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012"
152 fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012"
153 fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012"
157 // enable the message at line 1603 of file svcsock.c
158 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
159 <debugfs>/dynamic_debug/control
161 // enable all the messages in file svcsock.c
162 nullarbor:~ # echo -n 'file svcsock.c +p' >
163 <debugfs>/dynamic_debug/control
165 // enable all the messages in the NFS server module
166 nullarbor:~ # echo -n 'module nfsd +p' >
167 <debugfs>/dynamic_debug/control
169 // enable all 12 messages in the function svc_process()
170 nullarbor:~ # echo -n 'func svc_process +p' >
171 <debugfs>/dynamic_debug/control
173 // disable all 12 messages in the function svc_process()
174 nullarbor:~ # echo -n 'func svc_process -p' >
175 <debugfs>/dynamic_debug/control
177 See Documentation/admin-guide/dynamic-debug-howto.rst for additional
180 config DYNAMIC_DEBUG_CORE
181 bool "Enable core function of dynamic debug support"
183 depends on (DEBUG_FS || PROC_FS)
185 Enable core functional support of dynamic debug. It is useful
186 when you want to tie dynamic debug to your kernel modules with
187 DYNAMIC_DEBUG_MODULE defined for each of them, especially for
188 the case of embedded system where the kernel image size is
189 sensitive for people.
191 config SYMBOLIC_ERRNAME
192 bool "Support symbolic error names in printf"
195 If you say Y here, the kernel's printf implementation will
196 be able to print symbolic error names such as ENOSPC instead
197 of the number 28. It makes the kernel image slightly larger
198 (about 3KB), but can make the kernel logs easier to read.
200 config DEBUG_BUGVERBOSE
201 bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
202 depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE)
205 Say Y here to make BUG() panics output the file name and line number
206 of the BUG call as well as the EIP and oops trace. This aids
207 debugging but costs about 70-100K of memory.
209 endmenu # "printk and dmesg options"
212 bool "Kernel debugging"
214 Say Y here if you are developing drivers or trying to debug and
215 identify kernel problems.
218 bool "Miscellaneous debug code"
220 depends on DEBUG_KERNEL
222 Say Y here if you need to enable miscellaneous debug code that should
223 be under a more specific debug option but isn't.
225 menu "Compile-time checks and compiler options"
230 A kernel debug info option other than "None" has been selected
231 in the "Debug information" choice below, indicating that debug
232 information will be generated for build targets.
235 prompt "Debug information"
236 depends on DEBUG_KERNEL
238 Selecting something other than "None" results in a kernel image
239 that will include debugging info resulting in a larger kernel image.
240 This adds debug symbols to the kernel and modules (gcc -g), and
241 is needed if you intend to use kernel crashdump or binary object
242 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
244 Choose which version of DWARF debug info to emit. If unsure,
245 select "Toolchain default".
247 config DEBUG_INFO_NONE
248 bool "Disable debug information"
250 Do not build the kernel with debugging information, which will
251 result in a faster and smaller build.
253 config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT
254 bool "Rely on the toolchain's implicit default DWARF version"
257 The implicit default version of DWARF debug info produced by a
258 toolchain changes over time.
260 This can break consumers of the debug info that haven't upgraded to
261 support newer revisions, and prevent testing newer versions, but
262 those should be less common scenarios.
264 config DEBUG_INFO_DWARF4
265 bool "Generate DWARF Version 4 debuginfo"
268 Generate DWARF v4 debug info. This requires gcc 4.5+ and gdb 7.0+.
270 If you have consumers of DWARF debug info that are not ready for
271 newer revisions of DWARF, you may wish to choose this or have your
274 config DEBUG_INFO_DWARF5
275 bool "Generate DWARF Version 5 debuginfo"
277 depends on !CC_IS_CLANG || (CC_IS_CLANG && (AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502)))
279 Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc
280 5.0+ accepts the -gdwarf-5 flag but only had partial support for some
281 draft features until 7.0), and gdb 8.0+.
283 Changes to the structure of debug info in Version 5 allow for around
284 15-18% savings in resulting image and debug info section sizes as
285 compared to DWARF Version 4. DWARF Version 5 standardizes previous
286 extensions such as accelerators for symbol indexing and the format
287 for fission (.dwo/.dwp) files. Users may not want to select this
288 config if they rely on tooling that has not yet been updated to
289 support DWARF Version 5.
291 endchoice # "Debug information"
295 config DEBUG_INFO_REDUCED
296 bool "Reduce debugging information"
298 If you say Y here gcc is instructed to generate less debugging
299 information for structure types. This means that tools that
300 need full debugging information (like kgdb or systemtap) won't
301 be happy. But if you merely need debugging information to
302 resolve line numbers there is no loss. Advantage is that
303 build directory object sizes shrink dramatically over a full
304 DEBUG_INFO build and compile times are reduced too.
305 Only works with newer gcc versions.
307 config DEBUG_INFO_COMPRESSED
308 bool "Compressed debugging information"
309 depends on $(cc-option,-gz=zlib)
310 depends on $(ld-option,--compress-debug-sections=zlib)
312 Compress the debug information using zlib. Requires GCC 5.0+ or Clang
313 5.0+, binutils 2.26+, and zlib.
315 Users of dpkg-deb via scripts/package/builddeb may find an increase in
316 size of their debug .deb packages with this config set, due to the
317 debug info being compressed with zlib, then the object files being
318 recompressed with a different compression scheme. But this is still
319 preferable to setting $KDEB_COMPRESS to "none" which would be even
322 config DEBUG_INFO_SPLIT
323 bool "Produce split debuginfo in .dwo files"
324 depends on $(cc-option,-gsplit-dwarf)
326 Generate debug info into separate .dwo files. This significantly
327 reduces the build directory size for builds with DEBUG_INFO,
328 because it stores the information only once on disk in .dwo
329 files instead of multiple times in object files and executables.
330 In addition the debug information is also compressed.
332 Requires recent gcc (4.7+) and recent gdb/binutils.
333 Any tool that packages or reads debug information would need
334 to know about the .dwo files and include them.
335 Incompatible with older versions of ccache.
337 config DEBUG_INFO_BTF
338 bool "Generate BTF typeinfo"
339 depends on !DEBUG_INFO_SPLIT && !DEBUG_INFO_REDUCED
340 depends on !GCC_PLUGIN_RANDSTRUCT || COMPILE_TEST
341 depends on BPF_SYSCALL
342 depends on !DEBUG_INFO_DWARF5 || PAHOLE_VERSION >= 121
344 Generate deduplicated BTF type information from DWARF debug info.
345 Turning this on expects presence of pahole tool, which will convert
346 DWARF type info into equivalent deduplicated BTF type info.
348 config PAHOLE_HAS_SPLIT_BTF
349 def_bool PAHOLE_VERSION >= 119
351 config PAHOLE_HAS_BTF_TAG
352 def_bool PAHOLE_VERSION >= 123
353 depends on CC_IS_CLANG
355 Decide whether pahole emits btf_tag attributes (btf_type_tag and
356 btf_decl_tag) or not. Currently only clang compiler implements
357 these attributes, so make the config depend on CC_IS_CLANG.
359 config DEBUG_INFO_BTF_MODULES
361 depends on DEBUG_INFO_BTF && MODULES && PAHOLE_HAS_SPLIT_BTF
363 Generate compact split BTF type information for kernel modules.
365 config MODULE_ALLOW_BTF_MISMATCH
366 bool "Allow loading modules with non-matching BTF type info"
367 depends on DEBUG_INFO_BTF_MODULES
369 For modules whose split BTF does not match vmlinux, load without
370 BTF rather than refusing to load. The default behavior with
371 module BTF enabled is to reject modules with such mismatches;
372 this option will still load module BTF where possible but ignore
373 it when a mismatch is found.
376 bool "Provide GDB scripts for kernel debugging"
378 This creates the required links to GDB helper scripts in the
379 build directory. If you load vmlinux into gdb, the helper
380 scripts will be automatically imported by gdb as well, and
381 additional functions are available to analyze a Linux kernel
382 instance. See Documentation/dev-tools/gdb-kernel-debugging.rst
388 int "Warn for stack frames larger than"
390 default 2048 if GCC_PLUGIN_LATENT_ENTROPY
391 default 2048 if PARISC
392 default 1536 if (!64BIT && XTENSA)
393 default 1024 if !64BIT
394 default 2048 if 64BIT
396 Tell gcc to warn at build time for stack frames larger than this.
397 Setting this too low will cause a lot of warnings.
398 Setting it to 0 disables the warning.
400 config STRIP_ASM_SYMS
401 bool "Strip assembler-generated symbols during link"
404 Strip internal assembler-generated symbols during a link (symbols
405 that look like '.Lxxx') so they don't pollute the output of
406 get_wchan() and suchlike.
409 bool "Generate readable assembler code"
410 depends on DEBUG_KERNEL
413 Disable some compiler optimizations that tend to generate human unreadable
414 assembler output. This may make the kernel slightly slower, but it helps
415 to keep kernel developers who have to stare a lot at assembler listings
418 config HEADERS_INSTALL
419 bool "Install uapi headers to usr/include"
422 This option will install uapi headers (headers exported to user-space)
423 into the usr/include directory for use during the kernel build.
424 This is unneeded for building the kernel itself, but needed for some
425 user-space program samples. It is also needed by some features such
426 as uapi header sanity checks.
428 config DEBUG_SECTION_MISMATCH
429 bool "Enable full Section mismatch analysis"
432 The section mismatch analysis checks if there are illegal
433 references from one section to another section.
434 During linktime or runtime, some sections are dropped;
435 any use of code/data previously in these sections would
436 most likely result in an oops.
437 In the code, functions and variables are annotated with
438 __init,, etc. (see the full list in include/linux/init.h),
439 which results in the code/data being placed in specific sections.
440 The section mismatch analysis is always performed after a full
441 kernel build, and enabling this option causes the following
442 additional step to occur:
443 - Add the option -fno-inline-functions-called-once to gcc commands.
444 When inlining a function annotated with __init in a non-init
445 function, we would lose the section information and thus
446 the analysis would not catch the illegal reference.
447 This option tells gcc to inline less (but it does result in
450 config SECTION_MISMATCH_WARN_ONLY
451 bool "Make section mismatch errors non-fatal"
454 If you say N here, the build process will fail if there are any
455 section mismatch, instead of just throwing warnings.
459 config DEBUG_FORCE_FUNCTION_ALIGN_64B
460 bool "Force all function address 64B aligned"
461 depends on EXPERT && (X86_64 || ARM64 || PPC32 || PPC64 || ARC)
463 There are cases that a commit from one domain changes the function
464 address alignment of other domains, and cause magic performance
465 bump (regression or improvement). Enable this option will help to
466 verify if the bump is caused by function alignment changes, while
467 it will slightly increase the kernel size and affect icache usage.
469 It is mainly for debug and performance tuning use.
472 # Select this config option from the architecture Kconfig, if it
473 # is preferred to always offer frame pointers as a config
474 # option on the architecture (regardless of KERNEL_DEBUG):
476 config ARCH_WANT_FRAME_POINTERS
480 bool "Compile the kernel with frame pointers"
481 depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS
482 default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
484 If you say Y here the resulting kernel image will be slightly
485 larger and slower, but it gives very useful debugging information
486 in case of kernel bugs. (precise oopses/stacktraces/warnings)
491 config STACK_VALIDATION
492 bool "Compile-time stack metadata validation"
493 depends on HAVE_STACK_VALIDATION && UNWINDER_FRAME_POINTER
497 Validate frame pointer rules at compile-time. This helps ensure that
498 runtime stack traces are more reliable.
500 For more information, see
501 tools/objtool/Documentation/stack-validation.txt.
503 config NOINSTR_VALIDATION
505 depends on HAVE_NOINSTR_VALIDATION && DEBUG_ENTRY
510 bool "Generate vmlinux.map file when linking"
513 Selecting this option will pass "-Map=vmlinux.map" to ld
514 when linking vmlinux. That file can be useful for verifying
515 and debugging magic section games, and for seeing which
516 pieces of code get eliminated with
517 CONFIG_LD_DEAD_CODE_DATA_ELIMINATION.
519 config DEBUG_FORCE_WEAK_PER_CPU
520 bool "Force weak per-cpu definitions"
521 depends on DEBUG_KERNEL
523 s390 and alpha require percpu variables in modules to be
524 defined weak to work around addressing range issue which
525 puts the following two restrictions on percpu variable
528 1. percpu symbols must be unique whether static or not
529 2. percpu variables can't be defined inside a function
531 To ensure that generic code follows the above rules, this
532 option forces all percpu variables to be defined as weak.
534 endmenu # "Compiler options"
536 menu "Generic Kernel Debugging Instruments"
539 bool "Magic SysRq key"
542 If you say Y here, you will have some control over the system even
543 if the system crashes for example during kernel debugging (e.g., you
544 will be able to flush the buffer cache to disk, reboot the system
545 immediately or dump some status information). This is accomplished
546 by pressing various keys while holding SysRq (Alt+PrintScreen). It
547 also works on a serial console (on PC hardware at least), if you
548 send a BREAK and then within 5 seconds a command keypress. The
549 keys are documented in <file:Documentation/admin-guide/sysrq.rst>.
550 Don't say Y unless you really know what this hack does.
552 config MAGIC_SYSRQ_DEFAULT_ENABLE
553 hex "Enable magic SysRq key functions by default"
554 depends on MAGIC_SYSRQ
557 Specifies which SysRq key functions are enabled by default.
558 This may be set to 1 or 0 to enable or disable them all, or
559 to a bitmask as described in Documentation/admin-guide/sysrq.rst.
561 config MAGIC_SYSRQ_SERIAL
562 bool "Enable magic SysRq key over serial"
563 depends on MAGIC_SYSRQ
566 Many embedded boards have a disconnected TTL level serial which can
567 generate some garbage that can lead to spurious false sysrq detects.
568 This option allows you to decide whether you want to enable the
571 config MAGIC_SYSRQ_SERIAL_SEQUENCE
572 string "Char sequence that enables magic SysRq over serial"
573 depends on MAGIC_SYSRQ_SERIAL
576 Specifies a sequence of characters that can follow BREAK to enable
577 SysRq on a serial console.
579 If unsure, leave an empty string and the option will not be enabled.
582 bool "Debug Filesystem"
584 debugfs is a virtual file system that kernel developers use to put
585 debugging files into. Enable this option to be able to read and
586 write to these files.
588 For detailed documentation on the debugfs API, see
589 Documentation/filesystems/.
594 prompt "Debugfs default access"
596 default DEBUG_FS_ALLOW_ALL
598 This selects the default access restrictions for debugfs.
599 It can be overridden with kernel command line option
600 debugfs=[on,no-mount,off]. The restrictions apply for API access
601 and filesystem registration.
603 config DEBUG_FS_ALLOW_ALL
606 No restrictions apply. Both API and filesystem registration
607 is on. This is the normal default operation.
609 config DEBUG_FS_DISALLOW_MOUNT
610 bool "Do not register debugfs as filesystem"
612 The API is open but filesystem is not loaded. Clients can still do
613 their work and read with debug tools that do not need
616 config DEBUG_FS_ALLOW_NONE
619 Access is off. Clients get -PERM when trying to create nodes in
620 debugfs tree and debugfs is not registered as a filesystem.
621 Client can then back-off or continue without debugfs access.
625 source "lib/Kconfig.kgdb"
626 source "lib/Kconfig.ubsan"
627 source "lib/Kconfig.kcsan"
631 menu "Networking Debugging"
633 source "net/Kconfig.debug"
635 endmenu # "Networking Debugging"
637 menu "Memory Debugging"
639 source "mm/Kconfig.debug"
642 bool "Debug object operations"
643 depends on DEBUG_KERNEL
645 If you say Y here, additional code will be inserted into the
646 kernel to track the life time of various objects and validate
647 the operations on those objects.
649 config DEBUG_OBJECTS_SELFTEST
650 bool "Debug objects selftest"
651 depends on DEBUG_OBJECTS
653 This enables the selftest of the object debug code.
655 config DEBUG_OBJECTS_FREE
656 bool "Debug objects in freed memory"
657 depends on DEBUG_OBJECTS
659 This enables checks whether a k/v free operation frees an area
660 which contains an object which has not been deactivated
661 properly. This can make kmalloc/kfree-intensive workloads
664 config DEBUG_OBJECTS_TIMERS
665 bool "Debug timer objects"
666 depends on DEBUG_OBJECTS
668 If you say Y here, additional code will be inserted into the
669 timer routines to track the life time of timer objects and
670 validate the timer operations.
672 config DEBUG_OBJECTS_WORK
673 bool "Debug work objects"
674 depends on DEBUG_OBJECTS
676 If you say Y here, additional code will be inserted into the
677 work queue routines to track the life time of work objects and
678 validate the work operations.
680 config DEBUG_OBJECTS_RCU_HEAD
681 bool "Debug RCU callbacks objects"
682 depends on DEBUG_OBJECTS
684 Enable this to turn on debugging of RCU list heads (call_rcu() usage).
686 config DEBUG_OBJECTS_PERCPU_COUNTER
687 bool "Debug percpu counter objects"
688 depends on DEBUG_OBJECTS
690 If you say Y here, additional code will be inserted into the
691 percpu counter routines to track the life time of percpu counter
692 objects and validate the percpu counter operations.
694 config DEBUG_OBJECTS_ENABLE_DEFAULT
695 int "debug_objects bootup default value (0-1)"
698 depends on DEBUG_OBJECTS
700 Debug objects boot parameter default value
703 bool "Debug slab memory allocations"
704 depends on DEBUG_KERNEL && SLAB
706 Say Y here to have the kernel do limited verification on memory
707 allocation as well as poisoning memory on free to catch use of freed
708 memory. This can make kmalloc/kfree-intensive workloads much slower.
711 bool "SLUB debugging on by default"
712 depends on SLUB && SLUB_DEBUG
713 select STACKDEPOT_ALWAYS_INIT if STACKTRACE_SUPPORT
716 Boot with debugging on by default. SLUB boots by default with
717 the runtime debug capabilities switched off. Enabling this is
718 equivalent to specifying the "slub_debug" parameter on boot.
719 There is no support for more fine grained debug control like
720 possible with slub_debug=xxx. SLUB debugging may be switched
721 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
726 bool "Enable SLUB performance statistics"
727 depends on SLUB && SYSFS
729 SLUB statistics are useful to debug SLUBs allocation behavior in
730 order find ways to optimize the allocator. This should never be
731 enabled for production use since keeping statistics slows down
732 the allocator by a few percentage points. The slabinfo command
733 supports the determination of the most active slabs to figure
734 out which slabs are relevant to a particular load.
735 Try running: slabinfo -DA
737 config HAVE_DEBUG_KMEMLEAK
740 config DEBUG_KMEMLEAK
741 bool "Kernel memory leak detector"
742 depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK
744 select STACKTRACE if STACKTRACE_SUPPORT
748 Say Y here if you want to enable the memory leak
749 detector. The memory allocation/freeing is traced in a way
750 similar to the Boehm's conservative garbage collector, the
751 difference being that the orphan objects are not freed but
752 only shown in /sys/kernel/debug/kmemleak. Enabling this
753 feature will introduce an overhead to memory
754 allocations. See Documentation/dev-tools/kmemleak.rst for more
757 Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances
758 of finding leaks due to the slab objects poisoning.
760 In order to access the kmemleak file, debugfs needs to be
761 mounted (usually at /sys/kernel/debug).
763 config DEBUG_KMEMLEAK_MEM_POOL_SIZE
764 int "Kmemleak memory pool size"
765 depends on DEBUG_KMEMLEAK
769 Kmemleak must track all the memory allocations to avoid
770 reporting false positives. Since memory may be allocated or
771 freed before kmemleak is fully initialised, use a static pool
772 of metadata objects to track such callbacks. After kmemleak is
773 fully initialised, this memory pool acts as an emergency one
774 if slab allocations fail.
776 config DEBUG_KMEMLEAK_TEST
777 tristate "Simple test for the kernel memory leak detector"
778 depends on DEBUG_KMEMLEAK && m
780 This option enables a module that explicitly leaks memory.
784 config DEBUG_KMEMLEAK_DEFAULT_OFF
785 bool "Default kmemleak to off"
786 depends on DEBUG_KMEMLEAK
788 Say Y here to disable kmemleak by default. It can then be enabled
789 on the command line via kmemleak=on.
791 config DEBUG_KMEMLEAK_AUTO_SCAN
792 bool "Enable kmemleak auto scan thread on boot up"
794 depends on DEBUG_KMEMLEAK
796 Depending on the cpu, kmemleak scan may be cpu intensive and can
797 stall user tasks at times. This option enables/disables automatic
798 kmemleak scan at boot up.
800 Say N here to disable kmemleak auto scan thread to stop automatic
801 scanning. Disabling this option disables automatic reporting of
806 config DEBUG_STACK_USAGE
807 bool "Stack utilization instrumentation"
808 depends on DEBUG_KERNEL && !IA64
810 Enables the display of the minimum amount of free stack which each
811 task has ever had available in the sysrq-T and sysrq-P debug output.
813 This option will slow down process creation somewhat.
815 config SCHED_STACK_END_CHECK
816 bool "Detect stack corruption on calls to schedule()"
817 depends on DEBUG_KERNEL
820 This option checks for a stack overrun on calls to schedule().
821 If the stack end location is found to be over written always panic as
822 the content of the corrupted region can no longer be trusted.
823 This is to ensure no erroneous behaviour occurs which could result in
824 data corruption or a sporadic crash at a later stage once the region
825 is examined. The runtime overhead introduced is minimal.
827 config ARCH_HAS_DEBUG_VM_PGTABLE
830 An architecture should select this when it can successfully
831 build and run DEBUG_VM_PGTABLE.
835 depends on DEBUG_KERNEL
837 Enable this to turn on extended checks in the virtual-memory system
838 that may impact performance.
842 config DEBUG_VM_VMACACHE
843 bool "Debug VMA caching"
846 Enable this to turn on VMA caching debug information. Doing so
847 can cause significant overhead, so only enable it in non-production
853 bool "Debug VM red-black trees"
856 Enable VM red-black tree debugging information and extra validations.
860 config DEBUG_VM_PGFLAGS
861 bool "Debug page-flags operations"
864 Enables extra validation on page flags operations.
868 config DEBUG_VM_PGTABLE
869 bool "Debug arch page table for semantics compliance"
871 depends on ARCH_HAS_DEBUG_VM_PGTABLE
872 default y if DEBUG_VM
874 This option provides a debug method which can be used to test
875 architecture page table helper functions on various platforms in
876 verifying if they comply with expected generic MM semantics. This
877 will help architecture code in making sure that any changes or
878 new additions of these helpers still conform to expected
879 semantics of the generic MM. Platforms will have to opt in for
880 this through ARCH_HAS_DEBUG_VM_PGTABLE.
884 config ARCH_HAS_DEBUG_VIRTUAL
888 bool "Debug VM translations"
889 depends on DEBUG_KERNEL && ARCH_HAS_DEBUG_VIRTUAL
891 Enable some costly sanity checks in virtual to page code. This can
892 catch mistakes with virt_to_page() and friends.
896 config DEBUG_NOMMU_REGIONS
897 bool "Debug the global anon/private NOMMU mapping region tree"
898 depends on DEBUG_KERNEL && !MMU
900 This option causes the global tree of anonymous and private mapping
901 regions to be regularly checked for invalid topology.
903 config DEBUG_MEMORY_INIT
904 bool "Debug memory initialisation" if EXPERT
907 Enable this for additional checks during memory initialisation.
908 The sanity checks verify aspects of the VM such as the memory model
909 and other information provided by the architecture. Verbose
910 information will be printed at KERN_DEBUG loglevel depending
911 on the mminit_loglevel= command-line option.
915 config MEMORY_NOTIFIER_ERROR_INJECT
916 tristate "Memory hotplug notifier error injection module"
917 depends on MEMORY_HOTPLUG && NOTIFIER_ERROR_INJECTION
919 This option provides the ability to inject artificial errors to
920 memory hotplug notifier chain callbacks. It is controlled through
921 debugfs interface under /sys/kernel/debug/notifier-error-inject/memory
923 If the notifier call chain should be failed with some events
924 notified, write the error code to "actions/<notifier event>/error".
926 Example: Inject memory hotplug offline error (-12 == -ENOMEM)
928 # cd /sys/kernel/debug/notifier-error-inject/memory
929 # echo -12 > actions/MEM_GOING_OFFLINE/error
930 # echo offline > /sys/devices/system/memory/memoryXXX/state
931 bash: echo: write error: Cannot allocate memory
933 To compile this code as a module, choose M here: the module will
934 be called memory-notifier-error-inject.
938 config DEBUG_PER_CPU_MAPS
939 bool "Debug access to per_cpu maps"
940 depends on DEBUG_KERNEL
943 Say Y to verify that the per_cpu map being accessed has
944 been set up. This adds a fair amount of code to kernel memory
945 and decreases performance.
949 config DEBUG_KMAP_LOCAL
950 bool "Debug kmap_local temporary mappings"
951 depends on DEBUG_KERNEL && KMAP_LOCAL
953 This option enables additional error checking for the kmap_local
954 infrastructure. Disable for production use.
956 config ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
959 config DEBUG_KMAP_LOCAL_FORCE_MAP
960 bool "Enforce kmap_local temporary mappings"
961 depends on DEBUG_KERNEL && ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
963 select DEBUG_KMAP_LOCAL
965 This option enforces temporary mappings through the kmap_local
966 mechanism for non-highmem pages and on non-highmem systems.
967 Disable this for production systems!
970 bool "Highmem debugging"
971 depends on DEBUG_KERNEL && HIGHMEM
972 select DEBUG_KMAP_LOCAL_FORCE_MAP if ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
973 select DEBUG_KMAP_LOCAL
975 This option enables additional error checking for high memory
976 systems. Disable for production systems.
978 config HAVE_DEBUG_STACKOVERFLOW
981 config DEBUG_STACKOVERFLOW
982 bool "Check for stack overflows"
983 depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW
985 Say Y here if you want to check for overflows of kernel, IRQ
986 and exception stacks (if your architecture uses them). This
987 option will show detailed messages if free stack space drops
988 below a certain limit.
990 These kinds of bugs usually occur when call-chains in the
991 kernel get too deep, especially when interrupts are
994 Use this in cases where you see apparently random memory
995 corruption, especially if it appears in 'struct thread_info'
997 If in doubt, say "N".
999 source "lib/Kconfig.kasan"
1000 source "lib/Kconfig.kfence"
1002 endmenu # "Memory Debugging"
1005 bool "Debug shared IRQ handlers"
1006 depends on DEBUG_KERNEL
1008 Enable this to generate a spurious interrupt just before a shared
1009 interrupt handler is deregistered (generating one when registering
1010 is currently disabled). Drivers need to handle this correctly. Some
1011 don't and need to be caught.
1013 menu "Debug Oops, Lockups and Hangs"
1015 config PANIC_ON_OOPS
1016 bool "Panic on Oops"
1018 Say Y here to enable the kernel to panic when it oopses. This
1019 has the same effect as setting oops=panic on the kernel command
1022 This feature is useful to ensure that the kernel does not do
1023 anything erroneous after an oops which could result in data
1024 corruption or other issues.
1028 config PANIC_ON_OOPS_VALUE
1031 default 0 if !PANIC_ON_OOPS
1032 default 1 if PANIC_ON_OOPS
1034 config PANIC_TIMEOUT
1038 Set the timeout value (in seconds) until a reboot occurs when
1039 the kernel panics. If n = 0, then we wait forever. A timeout
1040 value n > 0 will wait n seconds before rebooting, while a timeout
1041 value n < 0 will reboot immediately.
1043 config LOCKUP_DETECTOR
1046 config SOFTLOCKUP_DETECTOR
1047 bool "Detect Soft Lockups"
1048 depends on DEBUG_KERNEL && !S390
1049 select LOCKUP_DETECTOR
1051 Say Y here to enable the kernel to act as a watchdog to detect
1054 Softlockups are bugs that cause the kernel to loop in kernel
1055 mode for more than 20 seconds, without giving other tasks a
1056 chance to run. The current stack trace is displayed upon
1057 detection and the system will stay locked up.
1059 config BOOTPARAM_SOFTLOCKUP_PANIC
1060 bool "Panic (Reboot) On Soft Lockups"
1061 depends on SOFTLOCKUP_DETECTOR
1063 Say Y here to enable the kernel to panic on "soft lockups",
1064 which are bugs that cause the kernel to loop in kernel
1065 mode for more than 20 seconds (configurable using the watchdog_thresh
1066 sysctl), without giving other tasks a chance to run.
1068 The panic can be used in combination with panic_timeout,
1069 to cause the system to reboot automatically after a
1070 lockup has been detected. This feature is useful for
1071 high-availability systems that have uptime guarantees and
1072 where a lockup must be resolved ASAP.
1076 config HARDLOCKUP_DETECTOR_PERF
1078 select SOFTLOCKUP_DETECTOR
1081 # Enables a timestamp based low pass filter to compensate for perf based
1082 # hard lockup detection which runs too fast due to turbo modes.
1084 config HARDLOCKUP_CHECK_TIMESTAMP
1088 # arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard
1089 # lockup detector rather than the perf based detector.
1091 config HARDLOCKUP_DETECTOR
1092 bool "Detect Hard Lockups"
1093 depends on DEBUG_KERNEL && !S390
1094 depends on HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_ARCH
1095 select LOCKUP_DETECTOR
1096 select HARDLOCKUP_DETECTOR_PERF if HAVE_HARDLOCKUP_DETECTOR_PERF
1098 Say Y here to enable the kernel to act as a watchdog to detect
1101 Hardlockups are bugs that cause the CPU to loop in kernel mode
1102 for more than 10 seconds, without letting other interrupts have a
1103 chance to run. The current stack trace is displayed upon detection
1104 and the system will stay locked up.
1106 config BOOTPARAM_HARDLOCKUP_PANIC
1107 bool "Panic (Reboot) On Hard Lockups"
1108 depends on HARDLOCKUP_DETECTOR
1110 Say Y here to enable the kernel to panic on "hard lockups",
1111 which are bugs that cause the kernel to loop in kernel
1112 mode with interrupts disabled for more than 10 seconds (configurable
1113 using the watchdog_thresh sysctl).
1117 config DETECT_HUNG_TASK
1118 bool "Detect Hung Tasks"
1119 depends on DEBUG_KERNEL
1120 default SOFTLOCKUP_DETECTOR
1122 Say Y here to enable the kernel to detect "hung tasks",
1123 which are bugs that cause the task to be stuck in
1124 uninterruptible "D" state indefinitely.
1126 When a hung task is detected, the kernel will print the
1127 current stack trace (which you should report), but the
1128 task will stay in uninterruptible state. If lockdep is
1129 enabled then all held locks will also be reported. This
1130 feature has negligible overhead.
1132 config DEFAULT_HUNG_TASK_TIMEOUT
1133 int "Default timeout for hung task detection (in seconds)"
1134 depends on DETECT_HUNG_TASK
1137 This option controls the default timeout (in seconds) used
1138 to determine when a task has become non-responsive and should
1141 It can be adjusted at runtime via the kernel.hung_task_timeout_secs
1142 sysctl or by writing a value to
1143 /proc/sys/kernel/hung_task_timeout_secs.
1145 A timeout of 0 disables the check. The default is two minutes.
1146 Keeping the default should be fine in most cases.
1148 config BOOTPARAM_HUNG_TASK_PANIC
1149 bool "Panic (Reboot) On Hung Tasks"
1150 depends on DETECT_HUNG_TASK
1152 Say Y here to enable the kernel to panic on "hung tasks",
1153 which are bugs that cause the kernel to leave a task stuck
1154 in uninterruptible "D" state.
1156 The panic can be used in combination with panic_timeout,
1157 to cause the system to reboot automatically after a
1158 hung task has been detected. This feature is useful for
1159 high-availability systems that have uptime guarantees and
1160 where a hung tasks must be resolved ASAP.
1165 bool "Detect Workqueue Stalls"
1166 depends on DEBUG_KERNEL
1168 Say Y here to enable stall detection on workqueues. If a
1169 worker pool doesn't make forward progress on a pending work
1170 item for over a given amount of time, 30s by default, a
1171 warning message is printed along with dump of workqueue
1172 state. This can be configured through kernel parameter
1173 "workqueue.watchdog_thresh" and its sysfs counterpart.
1176 tristate "Test module to generate lockups"
1179 This builds the "test_lockup" module that helps to make sure
1180 that watchdogs and lockup detectors are working properly.
1182 Depending on module parameters it could emulate soft or hard
1183 lockup, "hung task", or locking arbitrary lock for a long time.
1184 Also it could generate series of lockups with cooling-down periods.
1188 endmenu # "Debug lockups and hangs"
1190 menu "Scheduler Debugging"
1193 bool "Collect scheduler debugging info"
1194 depends on DEBUG_KERNEL && PROC_FS
1197 If you say Y here, the /proc/sched_debug file will be provided
1198 that can help debug the scheduler. The runtime overhead of this
1206 bool "Collect scheduler statistics"
1207 depends on DEBUG_KERNEL && PROC_FS
1210 If you say Y here, additional code will be inserted into the
1211 scheduler and related routines to collect statistics about
1212 scheduler behavior and provide them in /proc/schedstat. These
1213 stats may be useful for both tuning and debugging the scheduler
1214 If you aren't debugging the scheduler or trying to tune a specific
1215 application, you can say N to avoid the very slight overhead
1220 config DEBUG_TIMEKEEPING
1221 bool "Enable extra timekeeping sanity checking"
1223 This option will enable additional timekeeping sanity checks
1224 which may be helpful when diagnosing issues where timekeeping
1225 problems are suspected.
1227 This may include checks in the timekeeping hotpaths, so this
1228 option may have a (very small) performance impact to some
1233 config DEBUG_PREEMPT
1234 bool "Debug preemptible kernel"
1235 depends on DEBUG_KERNEL && PREEMPTION && TRACE_IRQFLAGS_SUPPORT
1238 If you say Y here then the kernel will use a debug variant of the
1239 commonly used smp_processor_id() function and will print warnings
1240 if kernel code uses it in a preemption-unsafe way. Also, the kernel
1241 will detect preemption count underflows.
1243 menu "Lock Debugging (spinlocks, mutexes, etc...)"
1245 config LOCK_DEBUGGING_SUPPORT
1247 depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
1250 config PROVE_LOCKING
1251 bool "Lock debugging: prove locking correctness"
1252 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1254 select DEBUG_SPINLOCK
1255 select DEBUG_MUTEXES if !PREEMPT_RT
1256 select DEBUG_RT_MUTEXES if RT_MUTEXES
1258 select DEBUG_WW_MUTEX_SLOWPATH
1259 select DEBUG_LOCK_ALLOC
1260 select PREEMPT_COUNT if !ARCH_NO_PREEMPT
1261 select TRACE_IRQFLAGS
1264 This feature enables the kernel to prove that all locking
1265 that occurs in the kernel runtime is mathematically
1266 correct: that under no circumstance could an arbitrary (and
1267 not yet triggered) combination of observed locking
1268 sequences (on an arbitrary number of CPUs, running an
1269 arbitrary number of tasks and interrupt contexts) cause a
1272 In short, this feature enables the kernel to report locking
1273 related deadlocks before they actually occur.
1275 The proof does not depend on how hard and complex a
1276 deadlock scenario would be to trigger: how many
1277 participant CPUs, tasks and irq-contexts would be needed
1278 for it to trigger. The proof also does not depend on
1279 timing: if a race and a resulting deadlock is possible
1280 theoretically (no matter how unlikely the race scenario
1281 is), it will be proven so and will immediately be
1282 reported by the kernel (once the event is observed that
1283 makes the deadlock theoretically possible).
1285 If a deadlock is impossible (i.e. the locking rules, as
1286 observed by the kernel, are mathematically correct), the
1287 kernel reports nothing.
1289 NOTE: this feature can also be enabled for rwlocks, mutexes
1290 and rwsems - in which case all dependencies between these
1291 different locking variants are observed and mapped too, and
1292 the proof of observed correctness is also maintained for an
1293 arbitrary combination of these separate locking variants.
1295 For more details, see Documentation/locking/lockdep-design.rst.
1297 config PROVE_RAW_LOCK_NESTING
1298 bool "Enable raw_spinlock - spinlock nesting checks"
1299 depends on PROVE_LOCKING
1302 Enable the raw_spinlock vs. spinlock nesting checks which ensure
1303 that the lock nesting rules for PREEMPT_RT enabled kernels are
1306 NOTE: There are known nesting problems. So if you enable this
1307 option expect lockdep splats until these problems have been fully
1308 addressed which is work in progress. This config switch allows to
1309 identify and analyze these problems. It will be removed and the
1310 check permanently enabled once the main issues have been fixed.
1312 If unsure, select N.
1315 bool "Lock usage statistics"
1316 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1318 select DEBUG_SPINLOCK
1319 select DEBUG_MUTEXES if !PREEMPT_RT
1320 select DEBUG_RT_MUTEXES if RT_MUTEXES
1321 select DEBUG_LOCK_ALLOC
1324 This feature enables tracking lock contention points
1326 For more details, see Documentation/locking/lockstat.rst
1328 This also enables lock events required by "perf lock",
1330 If you want to use "perf lock", you also need to turn on
1331 CONFIG_EVENT_TRACING.
1333 CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
1334 (CONFIG_LOCKDEP defines "acquire" and "release" events.)
1336 config DEBUG_RT_MUTEXES
1337 bool "RT Mutex debugging, deadlock detection"
1338 depends on DEBUG_KERNEL && RT_MUTEXES
1340 This allows rt mutex semantics violations and rt mutex related
1341 deadlocks (lockups) to be detected and reported automatically.
1343 config DEBUG_SPINLOCK
1344 bool "Spinlock and rw-lock debugging: basic checks"
1345 depends on DEBUG_KERNEL
1346 select UNINLINE_SPIN_UNLOCK
1348 Say Y here and build SMP to catch missing spinlock initialization
1349 and certain other kinds of spinlock errors commonly made. This is
1350 best used in conjunction with the NMI watchdog so that spinlock
1351 deadlocks are also debuggable.
1353 config DEBUG_MUTEXES
1354 bool "Mutex debugging: basic checks"
1355 depends on DEBUG_KERNEL && !PREEMPT_RT
1357 This feature allows mutex semantics violations to be detected and
1360 config DEBUG_WW_MUTEX_SLOWPATH
1361 bool "Wait/wound mutex debugging: Slowpath testing"
1362 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1363 select DEBUG_LOCK_ALLOC
1364 select DEBUG_SPINLOCK
1365 select DEBUG_MUTEXES if !PREEMPT_RT
1366 select DEBUG_RT_MUTEXES if PREEMPT_RT
1368 This feature enables slowpath testing for w/w mutex users by
1369 injecting additional -EDEADLK wound/backoff cases. Together with
1370 the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this
1371 will test all possible w/w mutex interface abuse with the
1372 exception of simply not acquiring all the required locks.
1373 Note that this feature can introduce significant overhead, so
1374 it really should not be enabled in a production or distro kernel,
1375 even a debug kernel. If you are a driver writer, enable it. If
1376 you are a distro, do not.
1379 bool "RW Semaphore debugging: basic checks"
1380 depends on DEBUG_KERNEL
1382 This debugging feature allows mismatched rw semaphore locks
1383 and unlocks to be detected and reported.
1385 config DEBUG_LOCK_ALLOC
1386 bool "Lock debugging: detect incorrect freeing of live locks"
1387 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1388 select DEBUG_SPINLOCK
1389 select DEBUG_MUTEXES if !PREEMPT_RT
1390 select DEBUG_RT_MUTEXES if RT_MUTEXES
1393 This feature will check whether any held lock (spinlock, rwlock,
1394 mutex or rwsem) is incorrectly freed by the kernel, via any of the
1395 memory-freeing routines (kfree(), kmem_cache_free(), free_pages(),
1396 vfree(), etc.), whether a live lock is incorrectly reinitialized via
1397 spin_lock_init()/mutex_init()/etc., or whether there is any lock
1398 held during task exit.
1402 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1407 config LOCKDEP_SMALL
1411 int "Bitsize for MAX_LOCKDEP_ENTRIES"
1412 depends on LOCKDEP && !LOCKDEP_SMALL
1416 Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message.
1418 config LOCKDEP_CHAINS_BITS
1419 int "Bitsize for MAX_LOCKDEP_CHAINS"
1420 depends on LOCKDEP && !LOCKDEP_SMALL
1424 Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message.
1426 config LOCKDEP_STACK_TRACE_BITS
1427 int "Bitsize for MAX_STACK_TRACE_ENTRIES"
1428 depends on LOCKDEP && !LOCKDEP_SMALL
1432 Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message.
1434 config LOCKDEP_STACK_TRACE_HASH_BITS
1435 int "Bitsize for STACK_TRACE_HASH_SIZE"
1436 depends on LOCKDEP && !LOCKDEP_SMALL
1440 Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES.
1442 config LOCKDEP_CIRCULAR_QUEUE_BITS
1443 int "Bitsize for elements in circular_queue struct"
1448 Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure.
1450 config DEBUG_LOCKDEP
1451 bool "Lock dependency engine debugging"
1452 depends on DEBUG_KERNEL && LOCKDEP
1453 select DEBUG_IRQFLAGS
1455 If you say Y here, the lock dependency engine will do
1456 additional runtime checks to debug itself, at the price
1457 of more runtime overhead.
1459 config DEBUG_ATOMIC_SLEEP
1460 bool "Sleep inside atomic section checking"
1461 select PREEMPT_COUNT
1462 depends on DEBUG_KERNEL
1463 depends on !ARCH_NO_PREEMPT
1465 If you say Y here, various routines which may sleep will become very
1466 noisy if they are called inside atomic sections: when a spinlock is
1467 held, inside an rcu read side critical section, inside preempt disabled
1468 sections, inside an interrupt, etc...
1470 config DEBUG_LOCKING_API_SELFTESTS
1471 bool "Locking API boot-time self-tests"
1472 depends on DEBUG_KERNEL
1474 Say Y here if you want the kernel to run a short self-test during
1475 bootup. The self-test checks whether common types of locking bugs
1476 are detected by debugging mechanisms or not. (if you disable
1477 lock debugging then those bugs won't be detected of course.)
1478 The following locking APIs are covered: spinlocks, rwlocks,
1481 config LOCK_TORTURE_TEST
1482 tristate "torture tests for locking"
1483 depends on DEBUG_KERNEL
1486 This option provides a kernel module that runs torture tests
1487 on kernel locking primitives. The kernel module may be built
1488 after the fact on the running kernel to be tested, if desired.
1490 Say Y here if you want kernel locking-primitive torture tests
1491 to be built into the kernel.
1492 Say M if you want these torture tests to build as a module.
1493 Say N if you are unsure.
1495 config WW_MUTEX_SELFTEST
1496 tristate "Wait/wound mutex selftests"
1498 This option provides a kernel module that runs tests on the
1499 on the struct ww_mutex locking API.
1501 It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction
1502 with this test harness.
1504 Say M if you want these self tests to build as a module.
1505 Say N if you are unsure.
1507 config SCF_TORTURE_TEST
1508 tristate "torture tests for smp_call_function*()"
1509 depends on DEBUG_KERNEL
1512 This option provides a kernel module that runs torture tests
1513 on the smp_call_function() family of primitives. The kernel
1514 module may be built after the fact on the running kernel to
1515 be tested, if desired.
1517 config CSD_LOCK_WAIT_DEBUG
1518 bool "Debugging for csd_lock_wait(), called from smp_call_function*()"
1519 depends on DEBUG_KERNEL
1523 This option enables debug prints when CPUs are slow to respond
1524 to the smp_call_function*() IPI wrappers. These debug prints
1525 include the IPI handler function currently executing (if any)
1526 and relevant stack traces.
1529 prompt "Lock debugging: prove subsystem device_lock() correctness"
1530 depends on PROVE_LOCKING
1532 For subsystems that have instrumented their usage of the device_lock()
1533 with nested annotations, enable lock dependency checking. The locking
1534 hierarchy 'subclass' identifiers are not compatible across
1535 sub-systems, so only one can be enabled at a time.
1537 config PROVE_NVDIMM_LOCKING
1539 depends on LIBNVDIMM
1541 Enable lockdep to validate nd_device_lock() usage.
1543 config PROVE_CXL_LOCKING
1547 Enable lockdep to validate cxl_device_lock() usage.
1551 endmenu # lock debugging
1553 config TRACE_IRQFLAGS
1554 depends on TRACE_IRQFLAGS_SUPPORT
1557 Enables hooks to interrupt enabling and disabling for
1558 either tracing or lock debugging.
1560 config TRACE_IRQFLAGS_NMI
1562 depends on TRACE_IRQFLAGS
1563 depends on TRACE_IRQFLAGS_NMI_SUPPORT
1565 config DEBUG_IRQFLAGS
1566 bool "Debug IRQ flag manipulation"
1568 Enables checks for potentially unsafe enabling or disabling of
1569 interrupts, such as calling raw_local_irq_restore() when interrupts
1573 bool "Stack backtrace support"
1574 depends on STACKTRACE_SUPPORT
1576 This option causes the kernel to create a /proc/pid/stack for
1577 every process, showing its current stack trace.
1578 It is also used by various kernel debugging features that require
1579 stack trace generation.
1581 config WARN_ALL_UNSEEDED_RANDOM
1582 bool "Warn for all uses of unseeded randomness"
1585 Some parts of the kernel contain bugs relating to their use of
1586 cryptographically secure random numbers before it's actually possible
1587 to generate those numbers securely. This setting ensures that these
1588 flaws don't go unnoticed, by enabling a message, should this ever
1589 occur. This will allow people with obscure setups to know when things
1590 are going wrong, so that they might contact developers about fixing
1593 Unfortunately, on some models of some architectures getting
1594 a fully seeded CRNG is extremely difficult, and so this can
1595 result in dmesg getting spammed for a surprisingly long
1596 time. This is really bad from a security perspective, and
1597 so architecture maintainers really need to do what they can
1598 to get the CRNG seeded sooner after the system is booted.
1599 However, since users cannot do anything actionable to
1600 address this, by default this option is disabled.
1602 Say Y here if you want to receive warnings for all uses of
1603 unseeded randomness. This will be of use primarily for
1604 those developers interested in improving the security of
1605 Linux kernels running on their architecture (or
1608 config DEBUG_KOBJECT
1609 bool "kobject debugging"
1610 depends on DEBUG_KERNEL
1612 If you say Y here, some extra kobject debugging messages will be sent
1615 config DEBUG_KOBJECT_RELEASE
1616 bool "kobject release debugging"
1617 depends on DEBUG_OBJECTS_TIMERS
1619 kobjects are reference counted objects. This means that their
1620 last reference count put is not predictable, and the kobject can
1621 live on past the point at which a driver decides to drop it's
1622 initial reference to the kobject gained on allocation. An
1623 example of this would be a struct device which has just been
1626 However, some buggy drivers assume that after such an operation,
1627 the memory backing the kobject can be immediately freed. This
1628 goes completely against the principles of a refcounted object.
1630 If you say Y here, the kernel will delay the release of kobjects
1631 on the last reference count to improve the visibility of this
1632 kind of kobject release bug.
1634 config HAVE_DEBUG_BUGVERBOSE
1637 menu "Debug kernel data structures"
1640 bool "Debug linked list manipulation"
1641 depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION
1643 Enable this to turn on extended checks in the linked-list
1649 bool "Debug priority linked list manipulation"
1650 depends on DEBUG_KERNEL
1652 Enable this to turn on extended checks in the priority-ordered
1653 linked-list (plist) walking routines. This checks the entire
1654 list multiple times during each manipulation.
1659 bool "Debug SG table operations"
1660 depends on DEBUG_KERNEL
1662 Enable this to turn on checks on scatter-gather tables. This can
1663 help find problems with drivers that do not properly initialize
1668 config DEBUG_NOTIFIERS
1669 bool "Debug notifier call chains"
1670 depends on DEBUG_KERNEL
1672 Enable this to turn on sanity checking for notifier call chains.
1673 This is most useful for kernel developers to make sure that
1674 modules properly unregister themselves from notifier chains.
1675 This is a relatively cheap check but if you care about maximum
1678 config BUG_ON_DATA_CORRUPTION
1679 bool "Trigger a BUG when data corruption is detected"
1682 Select this option if the kernel should BUG when it encounters
1683 data corruption in kernel memory structures when they get checked
1690 config DEBUG_CREDENTIALS
1691 bool "Debug credential management"
1692 depends on DEBUG_KERNEL
1694 Enable this to turn on some debug checking for credential
1695 management. The additional code keeps track of the number of
1696 pointers from task_structs to any given cred struct, and checks to
1697 see that this number never exceeds the usage count of the cred
1700 Furthermore, if SELinux is enabled, this also checks that the
1701 security pointer in the cred struct is never seen to be invalid.
1705 source "kernel/rcu/Kconfig.debug"
1707 config DEBUG_WQ_FORCE_RR_CPU
1708 bool "Force round-robin CPU selection for unbound work items"
1709 depends on DEBUG_KERNEL
1712 Workqueue used to implicitly guarantee that work items queued
1713 without explicit CPU specified are put on the local CPU. This
1714 guarantee is no longer true and while local CPU is still
1715 preferred work items may be put on foreign CPUs. Kernel
1716 parameter "workqueue.debug_force_rr_cpu" is added to force
1717 round-robin CPU selection to flush out usages which depend on the
1718 now broken guarantee. This config option enables the debug
1719 feature by default. When enabled, memory and cache locality will
1722 config CPU_HOTPLUG_STATE_CONTROL
1723 bool "Enable CPU hotplug state control"
1724 depends on DEBUG_KERNEL
1725 depends on HOTPLUG_CPU
1728 Allows to write steps between "offline" and "online" to the CPUs
1729 sysfs target file so states can be stepped granular. This is a debug
1730 option for now as the hotplug machinery cannot be stopped and
1731 restarted at arbitrary points yet.
1733 Say N if your are unsure.
1736 bool "Latency measuring infrastructure"
1737 depends on DEBUG_KERNEL
1738 depends on STACKTRACE_SUPPORT
1740 depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
1746 Enable this option if you want to use the LatencyTOP tool
1747 to find out which userspace is blocking on what kernel operations.
1749 source "kernel/trace/Kconfig"
1751 config PROVIDE_OHCI1394_DMA_INIT
1752 bool "Remote debugging over FireWire early on boot"
1753 depends on PCI && X86
1755 If you want to debug problems which hang or crash the kernel early
1756 on boot and the crashing machine has a FireWire port, you can use
1757 this feature to remotely access the memory of the crashed machine
1758 over FireWire. This employs remote DMA as part of the OHCI1394
1759 specification which is now the standard for FireWire controllers.
1761 With remote DMA, you can monitor the printk buffer remotely using
1762 firescope and access all memory below 4GB using fireproxy from gdb.
1763 Even controlling a kernel debugger is possible using remote DMA.
1767 If ohci1394_dma=early is used as boot parameter, it will initialize
1768 all OHCI1394 controllers which are found in the PCI config space.
1770 As all changes to the FireWire bus such as enabling and disabling
1771 devices cause a bus reset and thereby disable remote DMA for all
1772 devices, be sure to have the cable plugged and FireWire enabled on
1773 the debugging host before booting the debug target for debugging.
1775 This code (~1k) is freed after boot. By then, the firewire stack
1776 in charge of the OHCI-1394 controllers should be used instead.
1778 See Documentation/core-api/debugging-via-ohci1394.rst for more information.
1780 source "samples/Kconfig"
1782 config ARCH_HAS_DEVMEM_IS_ALLOWED
1785 config STRICT_DEVMEM
1786 bool "Filter access to /dev/mem"
1787 depends on MMU && DEVMEM
1788 depends on ARCH_HAS_DEVMEM_IS_ALLOWED || GENERIC_LIB_DEVMEM_IS_ALLOWED
1789 default y if PPC || X86 || ARM64
1791 If this option is disabled, you allow userspace (root) access to all
1792 of memory, including kernel and userspace memory. Accidental
1793 access to this is obviously disastrous, but specific access can
1794 be used by people debugging the kernel. Note that with PAT support
1795 enabled, even in this case there are restrictions on /dev/mem
1796 use due to the cache aliasing requirements.
1798 If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem
1799 file only allows userspace access to PCI space and the BIOS code and
1800 data regions. This is sufficient for dosemu and X and all common
1805 config IO_STRICT_DEVMEM
1806 bool "Filter I/O access to /dev/mem"
1807 depends on STRICT_DEVMEM
1809 If this option is disabled, you allow userspace (root) access to all
1810 io-memory regardless of whether a driver is actively using that
1811 range. Accidental access to this is obviously disastrous, but
1812 specific access can be used by people debugging kernel drivers.
1814 If this option is switched on, the /dev/mem file only allows
1815 userspace access to *idle* io-memory ranges (see /proc/iomem) This
1816 may break traditional users of /dev/mem (dosemu, legacy X, etc...)
1817 if the driver using a given range cannot be disabled.
1821 menu "$(SRCARCH) Debugging"
1823 source "arch/$(SRCARCH)/Kconfig.debug"
1827 menu "Kernel Testing and Coverage"
1829 source "lib/kunit/Kconfig"
1831 config NOTIFIER_ERROR_INJECTION
1832 tristate "Notifier error injection"
1833 depends on DEBUG_KERNEL
1836 This option provides the ability to inject artificial errors to
1837 specified notifier chain callbacks. It is useful to test the error
1838 handling of notifier call chain failures.
1842 config PM_NOTIFIER_ERROR_INJECT
1843 tristate "PM notifier error injection module"
1844 depends on PM && NOTIFIER_ERROR_INJECTION
1845 default m if PM_DEBUG
1847 This option provides the ability to inject artificial errors to
1848 PM notifier chain callbacks. It is controlled through debugfs
1849 interface /sys/kernel/debug/notifier-error-inject/pm
1851 If the notifier call chain should be failed with some events
1852 notified, write the error code to "actions/<notifier event>/error".
1854 Example: Inject PM suspend error (-12 = -ENOMEM)
1856 # cd /sys/kernel/debug/notifier-error-inject/pm/
1857 # echo -12 > actions/PM_SUSPEND_PREPARE/error
1858 # echo mem > /sys/power/state
1859 bash: echo: write error: Cannot allocate memory
1861 To compile this code as a module, choose M here: the module will
1862 be called pm-notifier-error-inject.
1866 config OF_RECONFIG_NOTIFIER_ERROR_INJECT
1867 tristate "OF reconfig notifier error injection module"
1868 depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION
1870 This option provides the ability to inject artificial errors to
1871 OF reconfig notifier chain callbacks. It is controlled
1872 through debugfs interface under
1873 /sys/kernel/debug/notifier-error-inject/OF-reconfig/
1875 If the notifier call chain should be failed with some events
1876 notified, write the error code to "actions/<notifier event>/error".
1878 To compile this code as a module, choose M here: the module will
1879 be called of-reconfig-notifier-error-inject.
1883 config NETDEV_NOTIFIER_ERROR_INJECT
1884 tristate "Netdev notifier error injection module"
1885 depends on NET && NOTIFIER_ERROR_INJECTION
1887 This option provides the ability to inject artificial errors to
1888 netdevice notifier chain callbacks. It is controlled through debugfs
1889 interface /sys/kernel/debug/notifier-error-inject/netdev
1891 If the notifier call chain should be failed with some events
1892 notified, write the error code to "actions/<notifier event>/error".
1894 Example: Inject netdevice mtu change error (-22 = -EINVAL)
1896 # cd /sys/kernel/debug/notifier-error-inject/netdev
1897 # echo -22 > actions/NETDEV_CHANGEMTU/error
1898 # ip link set eth0 mtu 1024
1899 RTNETLINK answers: Invalid argument
1901 To compile this code as a module, choose M here: the module will
1902 be called netdev-notifier-error-inject.
1906 config FUNCTION_ERROR_INJECTION
1908 depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES
1910 config FAULT_INJECTION
1911 bool "Fault-injection framework"
1912 depends on DEBUG_KERNEL
1914 Provide fault-injection framework.
1915 For more details, see Documentation/fault-injection/.
1918 bool "Fault-injection capability for kmalloc"
1919 depends on FAULT_INJECTION
1920 depends on SLAB || SLUB
1922 Provide fault-injection capability for kmalloc.
1924 config FAIL_PAGE_ALLOC
1925 bool "Fault-injection capability for alloc_pages()"
1926 depends on FAULT_INJECTION
1928 Provide fault-injection capability for alloc_pages().
1930 config FAULT_INJECTION_USERCOPY
1931 bool "Fault injection capability for usercopy functions"
1932 depends on FAULT_INJECTION
1934 Provides fault-injection capability to inject failures
1935 in usercopy functions (copy_from_user(), get_user(), ...).
1937 config FAIL_MAKE_REQUEST
1938 bool "Fault-injection capability for disk IO"
1939 depends on FAULT_INJECTION && BLOCK
1941 Provide fault-injection capability for disk IO.
1943 config FAIL_IO_TIMEOUT
1944 bool "Fault-injection capability for faking disk interrupts"
1945 depends on FAULT_INJECTION && BLOCK
1947 Provide fault-injection capability on end IO handling. This
1948 will make the block layer "forget" an interrupt as configured,
1949 thus exercising the error handling.
1951 Only works with drivers that use the generic timeout handling,
1952 for others it won't do anything.
1955 bool "Fault-injection capability for futexes"
1957 depends on FAULT_INJECTION && FUTEX
1959 Provide fault-injection capability for futexes.
1961 config FAULT_INJECTION_DEBUG_FS
1962 bool "Debugfs entries for fault-injection capabilities"
1963 depends on FAULT_INJECTION && SYSFS && DEBUG_FS
1965 Enable configuration of fault-injection capabilities via debugfs.
1967 config FAIL_FUNCTION
1968 bool "Fault-injection capability for functions"
1969 depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION
1971 Provide function-based fault-injection capability.
1972 This will allow you to override a specific function with a return
1973 with given return value. As a result, function caller will see
1974 an error value and have to handle it. This is useful to test the
1975 error handling in various subsystems.
1977 config FAIL_MMC_REQUEST
1978 bool "Fault-injection capability for MMC IO"
1979 depends on FAULT_INJECTION_DEBUG_FS && MMC
1981 Provide fault-injection capability for MMC IO.
1982 This will make the mmc core return data errors. This is
1983 useful to test the error handling in the mmc block device
1984 and to test how the mmc host driver handles retries from
1988 bool "Fault-injection capability for SunRPC"
1989 depends on FAULT_INJECTION_DEBUG_FS && SUNRPC_DEBUG
1991 Provide fault-injection capability for SunRPC and
1994 config FAULT_INJECTION_STACKTRACE_FILTER
1995 bool "stacktrace filter for fault-injection capabilities"
1996 depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
1999 depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
2001 Provide stacktrace filter for fault-injection capabilities
2003 config ARCH_HAS_KCOV
2006 An architecture should select this when it can successfully
2007 build and run with CONFIG_KCOV. This typically requires
2008 disabling instrumentation for some early boot code.
2010 config CC_HAS_SANCOV_TRACE_PC
2011 def_bool $(cc-option,-fsanitize-coverage=trace-pc)
2015 bool "Code coverage for fuzzing"
2016 depends on ARCH_HAS_KCOV
2017 depends on CC_HAS_SANCOV_TRACE_PC || GCC_PLUGINS
2018 depends on !ARCH_WANTS_NO_INSTR || HAVE_NOINSTR_HACK || \
2019 GCC_VERSION >= 120000 || CLANG_VERSION >= 130000
2021 select GCC_PLUGIN_SANCOV if !CC_HAS_SANCOV_TRACE_PC
2022 select OBJTOOL if HAVE_NOINSTR_HACK
2024 KCOV exposes kernel code coverage information in a form suitable
2025 for coverage-guided fuzzing (randomized testing).
2027 If RANDOMIZE_BASE is enabled, PC values will not be stable across
2028 different machines and across reboots. If you need stable PC values,
2029 disable RANDOMIZE_BASE.
2031 For more details, see Documentation/dev-tools/kcov.rst.
2033 config KCOV_ENABLE_COMPARISONS
2034 bool "Enable comparison operands collection by KCOV"
2036 depends on $(cc-option,-fsanitize-coverage=trace-cmp)
2038 KCOV also exposes operands of every comparison in the instrumented
2039 code along with operand sizes and PCs of the comparison instructions.
2040 These operands can be used by fuzzing engines to improve the quality
2041 of fuzzing coverage.
2043 config KCOV_INSTRUMENT_ALL
2044 bool "Instrument all code by default"
2048 If you are doing generic system call fuzzing (like e.g. syzkaller),
2049 then you will want to instrument the whole kernel and you should
2050 say y here. If you are doing more targeted fuzzing (like e.g.
2051 filesystem fuzzing with AFL) then you will want to enable coverage
2052 for more specific subsets of files, and should say n here.
2054 config KCOV_IRQ_AREA_SIZE
2055 hex "Size of interrupt coverage collection area in words"
2059 KCOV uses preallocated per-cpu areas to collect coverage from
2060 soft interrupts. This specifies the size of those areas in the
2061 number of unsigned long words.
2063 menuconfig RUNTIME_TESTING_MENU
2064 bool "Runtime Testing"
2067 if RUNTIME_TESTING_MENU
2070 tristate "Linux Kernel Dump Test Tool Module"
2073 This module enables testing of the different dumping mechanisms by
2074 inducing system failures at predefined crash points.
2075 If you don't need it: say N
2076 Choose M here to compile this code as a module. The module will be
2079 Documentation on how to use the module can be found in
2080 Documentation/fault-injection/provoke-crashes.rst
2082 config TEST_LIST_SORT
2083 tristate "Linked list sorting test" if !KUNIT_ALL_TESTS
2085 default KUNIT_ALL_TESTS
2087 Enable this to turn on 'list_sort()' function test. This test is
2088 executed only once during system boot (so affects only boot time),
2089 or at module load time.
2093 config TEST_MIN_HEAP
2094 tristate "Min heap test"
2095 depends on DEBUG_KERNEL || m
2097 Enable this to turn on min heap function tests. This test is
2098 executed only once during system boot (so affects only boot time),
2099 or at module load time.
2104 tristate "Array-based sort test" if !KUNIT_ALL_TESTS
2106 default KUNIT_ALL_TESTS
2108 This option enables the self-test function of 'sort()' at boot,
2109 or at module load time.
2114 tristate "64bit/32bit division and modulo test"
2115 depends on DEBUG_KERNEL || m
2117 Enable this to turn on 'do_div()' function test. This test is
2118 executed only once during system boot (so affects only boot time),
2119 or at module load time.
2123 config KPROBES_SANITY_TEST
2124 tristate "Kprobes sanity tests" if !KUNIT_ALL_TESTS
2125 depends on DEBUG_KERNEL
2128 default KUNIT_ALL_TESTS
2130 This option provides for testing basic kprobes functionality on
2131 boot. Samples of kprobe and kretprobe are inserted and
2132 verified for functionality.
2134 Say N if you are unsure.
2136 config FPROBE_SANITY_TEST
2137 bool "Self test for fprobe"
2138 depends on DEBUG_KERNEL
2142 This option will enable testing the fprobe when the system boot.
2143 A series of tests are made to verify that the fprobe is functioning
2146 Say N if you are unsure.
2148 config BACKTRACE_SELF_TEST
2149 tristate "Self test for the backtrace code"
2150 depends on DEBUG_KERNEL
2152 This option provides a kernel module that can be used to test
2153 the kernel stack backtrace code. This option is not useful
2154 for distributions or general kernels, but only for kernel
2155 developers working on architecture code.
2157 Note that if you want to also test saved backtraces, you will
2158 have to enable STACKTRACE as well.
2160 Say N if you are unsure.
2162 config TEST_REF_TRACKER
2163 tristate "Self test for reference tracker"
2164 depends on DEBUG_KERNEL && STACKTRACE_SUPPORT
2167 This option provides a kernel module performing tests
2168 using reference tracker infrastructure.
2170 Say N if you are unsure.
2173 tristate "Red-Black tree test"
2174 depends on DEBUG_KERNEL
2176 A benchmark measuring the performance of the rbtree library.
2177 Also includes rbtree invariant checks.
2179 config REED_SOLOMON_TEST
2180 tristate "Reed-Solomon library test"
2181 depends on DEBUG_KERNEL || m
2183 select REED_SOLOMON_ENC16
2184 select REED_SOLOMON_DEC16
2186 This option enables the self-test function of rslib at boot,
2187 or at module load time.
2191 config INTERVAL_TREE_TEST
2192 tristate "Interval tree test"
2193 depends on DEBUG_KERNEL
2194 select INTERVAL_TREE
2196 A benchmark measuring the performance of the interval tree library
2199 tristate "Per cpu operations test"
2200 depends on m && DEBUG_KERNEL
2202 Enable this option to build test module which validates per-cpu
2207 config ATOMIC64_SELFTEST
2208 tristate "Perform an atomic64_t self-test"
2210 Enable this option to test the atomic64_t functions at boot or
2211 at module load time.
2215 config ASYNC_RAID6_TEST
2216 tristate "Self test for hardware accelerated raid6 recovery"
2217 depends on ASYNC_RAID6_RECOV
2220 This is a one-shot self test that permutes through the
2221 recovery of all the possible two disk failure scenarios for a
2222 N-disk array. Recovery is performed with the asynchronous
2223 raid6 recovery routines, and will optionally use an offload
2224 engine if one is available.
2229 tristate "Test functions located in the hexdump module at runtime"
2231 config STRING_SELFTEST
2232 tristate "Test string functions at runtime"
2234 config TEST_STRING_HELPERS
2235 tristate "Test functions located in the string_helpers module at runtime"
2238 tristate "Test strscpy*() family of functions at runtime"
2241 tristate "Test kstrto*() family of functions at runtime"
2244 tristate "Test printf() family of functions at runtime"
2247 tristate "Test scanf() family of functions at runtime"
2250 tristate "Test bitmap_*() family of functions at runtime"
2252 Enable this option to test the bitmap functions at boot.
2257 tristate "Test functions located in the uuid module at runtime"
2260 tristate "Test the XArray code at runtime"
2262 config TEST_RHASHTABLE
2263 tristate "Perform selftest on resizable hash table"
2265 Enable this option to test the rhashtable functions at boot.
2270 tristate "Perform selftest on siphash functions"
2272 Enable this option to test the kernel's siphash (<linux/siphash.h>) hash
2273 functions on boot (or module load).
2275 This is intended to help people writing architecture-specific
2276 optimized versions. If unsure, say N.
2279 tristate "Perform selftest on IDA functions"
2282 tristate "Perform selftest on priority array manager"
2285 Enable this option to test priority array manager on boot
2290 config TEST_IRQ_TIMINGS
2291 bool "IRQ timings selftest"
2292 depends on IRQ_TIMINGS
2294 Enable this option to test the irq timings code on boot.
2299 tristate "Test module loading with 'hello world' module"
2302 This builds the "test_module" module that emits "Hello, world"
2303 on printk when loaded. It is designed to be used for basic
2304 evaluation of the module loading subsystem (for example when
2305 validating module verification). It lacks any extra dependencies,
2306 and will not normally be loaded by the system unless explicitly
2312 tristate "Test module for compilation of bitops operations"
2315 This builds the "test_bitops" module that is much like the
2316 TEST_LKM module except that it does a basic exercise of the
2317 set/clear_bit macros and get_count_order/long to make sure there are
2318 no compiler warnings from C=1 sparse checker or -Wextra
2319 compilations. It has no dependencies and doesn't run or load unless
2320 explicitly requested by name. for example: modprobe test_bitops.
2325 tristate "Test module for stress/performance analysis of vmalloc allocator"
2330 This builds the "test_vmalloc" module that should be used for
2331 stress and performance analysis. So, any new change for vmalloc
2332 subsystem can be evaluated from performance and stability point
2337 config TEST_USER_COPY
2338 tristate "Test user/kernel boundary protections"
2341 This builds the "test_user_copy" module that runs sanity checks
2342 on the copy_to/from_user infrastructure, making sure basic
2343 user/kernel boundary testing is working. If it fails to load,
2344 a regression has been detected in the user/kernel memory boundary
2350 tristate "Test BPF filter functionality"
2353 This builds the "test_bpf" module that runs various test vectors
2354 against the BPF interpreter or BPF JIT compiler depending on the
2355 current setting. This is in particular useful for BPF JIT compiler
2356 development, but also to run regression tests against changes in
2357 the interpreter code. It also enables test stubs for eBPF maps and
2358 verifier used by user space verifier testsuite.
2362 config TEST_BLACKHOLE_DEV
2363 tristate "Test blackhole netdev functionality"
2366 This builds the "test_blackhole_dev" module that validates the
2367 data path through this blackhole netdev.
2371 config FIND_BIT_BENCHMARK
2372 tristate "Test find_bit functions"
2374 This builds the "test_find_bit" module that measure find_*_bit()
2375 functions performance.
2379 config TEST_FIRMWARE
2380 tristate "Test firmware loading via userspace interface"
2381 depends on FW_LOADER
2383 This builds the "test_firmware" module that creates a userspace
2384 interface for testing firmware loading. This can be used to
2385 control the triggering of firmware loading without needing an
2386 actual firmware-using device. The contents can be rechecked by
2392 tristate "sysctl test driver"
2393 depends on PROC_SYSCTL
2395 This builds the "test_sysctl" module. This driver enables to test the
2396 proc sysctl interfaces available to drivers safely without affecting
2397 production knobs which might alter system functionality.
2401 config BITFIELD_KUNIT
2402 tristate "KUnit test bitfield functions at runtime" if !KUNIT_ALL_TESTS
2404 default KUNIT_ALL_TESTS
2406 Enable this option to test the bitfield functions at boot.
2408 KUnit tests run during boot and output the results to the debug log
2409 in TAP format (http://testanything.org/). Only useful for kernel devs
2410 running the KUnit test harness, and not intended for inclusion into a
2413 For more information on KUnit and unit tests in general please refer
2414 to the KUnit documentation in Documentation/dev-tools/kunit/.
2418 config HASH_KUNIT_TEST
2419 tristate "KUnit Test for integer hash functions" if !KUNIT_ALL_TESTS
2421 default KUNIT_ALL_TESTS
2423 Enable this option to test the kernel's string (<linux/stringhash.h>), and
2424 integer (<linux/hash.h>) hash functions on boot.
2426 KUnit tests run during boot and output the results to the debug log
2427 in TAP format (https://testanything.org/). Only useful for kernel devs
2428 running the KUnit test harness, and not intended for inclusion into a
2431 For more information on KUnit and unit tests in general please refer
2432 to the KUnit documentation in Documentation/dev-tools/kunit/.
2434 This is intended to help people writing architecture-specific
2435 optimized versions. If unsure, say N.
2437 config RESOURCE_KUNIT_TEST
2438 tristate "KUnit test for resource API" if !KUNIT_ALL_TESTS
2440 default KUNIT_ALL_TESTS
2442 This builds the resource API unit test.
2443 Tests the logic of API provided by resource.c and ioport.h.
2444 For more information on KUnit and unit tests in general please refer
2445 to the KUnit documentation in Documentation/dev-tools/kunit/.
2449 config SYSCTL_KUNIT_TEST
2450 tristate "KUnit test for sysctl" if !KUNIT_ALL_TESTS
2452 default KUNIT_ALL_TESTS
2454 This builds the proc sysctl unit test, which runs on boot.
2455 Tests the API contract and implementation correctness of sysctl.
2456 For more information on KUnit and unit tests in general please refer
2457 to the KUnit documentation in Documentation/dev-tools/kunit/.
2461 config LIST_KUNIT_TEST
2462 tristate "KUnit Test for Kernel Linked-list structures" if !KUNIT_ALL_TESTS
2464 default KUNIT_ALL_TESTS
2466 This builds the linked list KUnit test suite.
2467 It tests that the API and basic functionality of the list_head type
2468 and associated macros.
2470 KUnit tests run during boot and output the results to the debug log
2471 in TAP format (https://testanything.org/). Only useful for kernel devs
2472 running the KUnit test harness, and not intended for inclusion into a
2475 For more information on KUnit and unit tests in general please refer
2476 to the KUnit documentation in Documentation/dev-tools/kunit/.
2480 config LINEAR_RANGES_TEST
2481 tristate "KUnit test for linear_ranges"
2483 select LINEAR_RANGES
2485 This builds the linear_ranges unit test, which runs on boot.
2486 Tests the linear_ranges logic correctness.
2487 For more information on KUnit and unit tests in general please refer
2488 to the KUnit documentation in Documentation/dev-tools/kunit/.
2492 config CMDLINE_KUNIT_TEST
2493 tristate "KUnit test for cmdline API" if !KUNIT_ALL_TESTS
2495 default KUNIT_ALL_TESTS
2497 This builds the cmdline API unit test.
2498 Tests the logic of API provided by cmdline.c.
2499 For more information on KUnit and unit tests in general please refer
2500 to the KUnit documentation in Documentation/dev-tools/kunit/.
2505 tristate "KUnit test for bits.h" if !KUNIT_ALL_TESTS
2507 default KUNIT_ALL_TESTS
2509 This builds the bits unit test.
2510 Tests the logic of macros defined in bits.h.
2511 For more information on KUnit and unit tests in general please refer
2512 to the KUnit documentation in Documentation/dev-tools/kunit/.
2516 config SLUB_KUNIT_TEST
2517 tristate "KUnit test for SLUB cache error detection" if !KUNIT_ALL_TESTS
2518 depends on SLUB_DEBUG && KUNIT
2519 default KUNIT_ALL_TESTS
2521 This builds SLUB allocator unit test.
2522 Tests SLUB cache debugging functionality.
2523 For more information on KUnit and unit tests in general please refer
2524 to the KUnit documentation in Documentation/dev-tools/kunit/.
2528 config RATIONAL_KUNIT_TEST
2529 tristate "KUnit test for rational.c" if !KUNIT_ALL_TESTS
2530 depends on KUNIT && RATIONAL
2531 default KUNIT_ALL_TESTS
2533 This builds the rational math unit test.
2534 For more information on KUnit and unit tests in general please refer
2535 to the KUnit documentation in Documentation/dev-tools/kunit/.
2539 config MEMCPY_KUNIT_TEST
2540 tristate "Test memcpy(), memmove(), and memset() functions at runtime" if !KUNIT_ALL_TESTS
2542 default KUNIT_ALL_TESTS
2544 Builds unit tests for memcpy(), memmove(), and memset() functions.
2545 For more information on KUnit and unit tests in general please refer
2546 to the KUnit documentation in Documentation/dev-tools/kunit/.
2550 config OVERFLOW_KUNIT_TEST
2551 tristate "Test check_*_overflow() functions at runtime" if !KUNIT_ALL_TESTS
2553 default KUNIT_ALL_TESTS
2555 Builds unit tests for the check_*_overflow(), size_*(), allocation, and
2558 For more information on KUnit and unit tests in general please refer
2559 to the KUnit documentation in Documentation/dev-tools/kunit/.
2563 config STACKINIT_KUNIT_TEST
2564 tristate "Test level of stack variable initialization" if !KUNIT_ALL_TESTS
2566 default KUNIT_ALL_TESTS
2568 Test if the kernel is zero-initializing stack variables and
2569 padding. Coverage is controlled by compiler flags,
2570 CONFIG_INIT_STACK_ALL_PATTERN, CONFIG_INIT_STACK_ALL_ZERO,
2571 CONFIG_GCC_PLUGIN_STRUCTLEAK, CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF,
2572 or CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL.
2575 tristate "udelay test driver"
2577 This builds the "udelay_test" module that helps to make sure
2578 that udelay() is working properly.
2582 config TEST_STATIC_KEYS
2583 tristate "Test static keys"
2586 Test the static key interfaces.
2591 tristate "kmod stress tester"
2593 depends on NETDEVICES && NET_CORE && INET # for TUN
2595 depends on PAGE_SIZE_LESS_THAN_256KB # for BTRFS
2601 Test the kernel's module loading mechanism: kmod. kmod implements
2602 support to load modules using the Linux kernel's usermode helper.
2603 This test provides a series of tests against kmod.
2605 Although technically you can either build test_kmod as a module or
2606 into the kernel we disallow building it into the kernel since
2607 it stress tests request_module() and this will very likely cause
2608 some issues by taking over precious threads available from other
2609 module load requests, ultimately this could be fatal.
2613 tools/testing/selftests/kmod/kmod.sh --help
2617 config TEST_DEBUG_VIRTUAL
2618 tristate "Test CONFIG_DEBUG_VIRTUAL feature"
2619 depends on DEBUG_VIRTUAL
2621 Test the kernel's ability to detect incorrect calls to
2622 virt_to_phys() done against the non-linear part of the
2623 kernel's virtual address map.
2627 config TEST_MEMCAT_P
2628 tristate "Test memcat_p() helper function"
2630 Test the memcat_p() helper for correctly merging two
2631 pointer arrays together.
2635 config TEST_LIVEPATCH
2636 tristate "Test livepatching"
2638 depends on DYNAMIC_DEBUG
2639 depends on LIVEPATCH
2642 Test kernel livepatching features for correctness. The tests will
2643 load test modules that will be livepatched in various scenarios.
2645 To run all the livepatching tests:
2647 make -C tools/testing/selftests TARGETS=livepatch run_tests
2649 Alternatively, individual tests may be invoked:
2651 tools/testing/selftests/livepatch/test-callbacks.sh
2652 tools/testing/selftests/livepatch/test-livepatch.sh
2653 tools/testing/selftests/livepatch/test-shadow-vars.sh
2658 tristate "Perform selftest on object aggreration manager"
2662 Enable this option to test object aggregation manager on boot
2666 tristate "Test heap/page initialization"
2668 Test if the kernel is zero-initializing heap and page allocations.
2669 This can be useful to test init_on_alloc and init_on_free features.
2674 tristate "Test HMM (Heterogeneous Memory Management)"
2675 depends on TRANSPARENT_HUGEPAGE
2676 depends on DEVICE_PRIVATE
2680 This is a pseudo device driver solely for testing HMM.
2681 Say M here if you want to build the HMM test module.
2682 Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.
2686 config TEST_FREE_PAGES
2687 tristate "Test freeing pages"
2689 Test that a memory leak does not occur due to a race between
2690 freeing a block of pages and a speculative page reference.
2691 Loading this module is safe if your kernel has the bug fixed.
2692 If the bug is not fixed, it will leak gigabytes of memory and
2693 probably OOM your system.
2696 tristate "Test floating point operations in kernel space"
2697 depends on X86 && !KCOV_INSTRUMENT_ALL
2699 Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
2700 which will trigger a sequence of floating point operations. This is used
2701 for self-testing floating point control register setting in
2706 config TEST_CLOCKSOURCE_WATCHDOG
2707 tristate "Test clocksource watchdog in kernel space"
2708 depends on CLOCKSOURCE_WATCHDOG
2710 Enable this option to create a kernel module that will trigger
2711 a test of the clocksource watchdog. This module may be loaded
2712 via modprobe or insmod in which case it will run upon being
2713 loaded, or it may be built in, in which case it will run
2718 endif # RUNTIME_TESTING_MENU
2720 config ARCH_USE_MEMTEST
2723 An architecture should select this when it uses early_memtest()
2724 during boot process.
2728 depends on ARCH_USE_MEMTEST
2730 This option adds a kernel parameter 'memtest', which allows memtest
2731 to be set and executed.
2732 memtest=0, mean disabled; -- default
2733 memtest=1, mean do 1 test pattern;
2735 memtest=17, mean do 17 test patterns.
2736 If you are unsure how to answer this question, answer N.
2740 config HYPERV_TESTING
2741 bool "Microsoft Hyper-V driver testing"
2743 depends on HYPERV && DEBUG_FS
2745 Select this option to enable Hyper-V vmbus testing.
2747 endmenu # "Kernel Testing and Coverage"
2749 source "Documentation/Kconfig"
2751 endmenu # Kernel hacking
projects / linux-2.6-microblaze.git / blob