2013-07-02 04:04:49 +08:00
|
|
|
menu "printk and dmesg options"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config PRINTK_TIME
|
|
|
|
bool "Show timing information on printks"
|
2006-12-07 12:36:38 +08:00
|
|
|
depends on PRINTK
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2012-05-10 10:30:45 +08:00
|
|
|
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
|
|
|
|
parameter printk.time=1. See Documentation/kernel-parameters.txt
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2014-08-07 07:09:01 +08:00
|
|
|
config MESSAGE_LOGLEVEL_DEFAULT
|
2011-03-23 07:34:23 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:49 +08:00
|
|
|
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
|
|
|
|
depends on DEBUG_FS
|
|
|
|
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,
|
|
|
|
which is contained in the 'debugfs' filesystem. Thus, the debugfs
|
|
|
|
filesystem must first be mounted before making use of this feature.
|
|
|
|
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
|
|
|
|
flags : '=p' means the line is turned 'on' for printing
|
|
|
|
format : the format used for the debug statement
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
See Documentation/dynamic-debug-howto.txt for additional information.
|
|
|
|
|
|
|
|
endmenu # "printk and dmesg options"
|
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
menu "Compile-time checks and compiler options"
|
|
|
|
|
|
|
|
config DEBUG_INFO
|
|
|
|
bool "Compile the kernel with debug info"
|
2014-02-05 04:20:01 +08:00
|
|
|
depends on DEBUG_KERNEL && !COMPILE_TEST
|
2013-07-02 04:04:46 +08:00
|
|
|
help
|
|
|
|
If you say Y here the resulting kernel image will include
|
|
|
|
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.
|
|
|
|
|
|
|
|
config DEBUG_INFO_REDUCED
|
|
|
|
bool "Reduce debugging information"
|
|
|
|
depends on DEBUG_INFO
|
|
|
|
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.
|
|
|
|
|
2014-07-31 02:50:18 +08:00
|
|
|
config DEBUG_INFO_SPLIT
|
|
|
|
bool "Produce split debuginfo in .dwo files"
|
|
|
|
depends on DEBUG_INFO
|
|
|
|
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.
|
|
|
|
|
2014-07-31 02:50:19 +08:00
|
|
|
config DEBUG_INFO_DWARF4
|
|
|
|
bool "Generate dwarf4 debuginfo"
|
|
|
|
depends on DEBUG_INFO
|
|
|
|
help
|
|
|
|
Generate dwarf4 debug info. This requires recent versions
|
|
|
|
of gcc and gdb. It makes the debug information larger.
|
|
|
|
But it significantly improves the success of resolving
|
|
|
|
variables in gdb on optimized code.
|
|
|
|
|
2015-02-18 05:46:36 +08:00
|
|
|
config GDB_SCRIPTS
|
|
|
|
bool "Provide GDB scripts for kernel debugging"
|
|
|
|
depends on DEBUG_INFO
|
|
|
|
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
|
|
|
|
instance. See Documentation/gdb-kernel-debugging.txt for further
|
|
|
|
details.
|
|
|
|
|
2007-10-25 16:06:13 +08:00
|
|
|
config ENABLE_WARN_DEPRECATED
|
|
|
|
bool "Enable __deprecated logic"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Enable the __deprecated logic in the kernel build.
|
|
|
|
Disable this to suppress the "warning: 'foo' is deprecated
|
|
|
|
(declared at kernel/power/somefile.c:1234)" messages.
|
|
|
|
|
2006-08-15 13:43:18 +08:00
|
|
|
config ENABLE_MUST_CHECK
|
|
|
|
bool "Enable __must_check logic"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Enable the __must_check logic in the kernel build. Disable this to
|
|
|
|
suppress the "warning: ignoring return value of 'foo', declared with
|
|
|
|
attribute warn_unused_result" messages.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-02-22 22:15:03 +08:00
|
|
|
config FRAME_WARN
|
|
|
|
int "Warn for stack frames larger than (needs gcc 4.4)"
|
|
|
|
range 0 8192
|
2015-10-23 04:32:24 +08:00
|
|
|
default 0 if KASAN
|
2016-10-28 08:46:41 +08:00
|
|
|
default 2048 if GCC_PLUGIN_LATENT_ENTROPY
|
2008-02-22 22:15:03 +08:00
|
|
|
default 1024 if !64BIT
|
|
|
|
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.
|
|
|
|
Requires gcc 4.4
|
|
|
|
|
2009-09-19 03:49:22 +08:00
|
|
|
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.
|
|
|
|
|
2012-03-29 02:51:18 +08:00
|
|
|
config READABLE_ASM
|
|
|
|
bool "Generate readable assembler code"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
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.
|
|
|
|
|
2006-06-28 19:26:45 +08:00
|
|
|
config UNUSED_SYMBOLS
|
|
|
|
bool "Enable unused/obsolete exported symbols"
|
|
|
|
default y if X86
|
|
|
|
help
|
|
|
|
Unused but exported symbols make the kernel needlessly bigger. For
|
|
|
|
that reason most of these unused exports will soon be removed. This
|
|
|
|
option is provided temporarily to provide a transition period in case
|
|
|
|
some external kernel module needs one of these symbols anyway. If you
|
|
|
|
encounter such a case in your module, consider if you are actually
|
|
|
|
using the right API. (rationale: since nobody in the kernel is using
|
|
|
|
this in a module, there is a pretty good chance it's actually the
|
|
|
|
wrong interface to use). If you really need the symbol, please send a
|
|
|
|
mail to the linux kernel mailing list mentioning the symbol and why
|
|
|
|
you really need it, and what the merge plan to the mainline kernel for
|
|
|
|
your module is.
|
|
|
|
|
mm/page_owner: keep track of page owners
This is the page owner tracking code which is introduced so far ago. It
is resident on Andrew's tree, though, nobody tried to upstream so it
remain as is. Our company uses this feature actively to debug memory leak
or to find a memory hogger so I decide to upstream this feature.
This functionality help us to know who allocates the page. When
allocating a page, we store some information about allocation in extra
memory. Later, if we need to know status of all pages, we can get and
analyze it from this stored information.
In previous version of this feature, extra memory is statically defined in
struct page, but, in this version, extra memory is allocated outside of
struct page. It enables us to turn on/off this feature at boottime
without considerable memory waste.
Although we already have tracepoint for tracing page allocation/free,
using it to analyze page owner is rather complex. We need to enlarge the
trace buffer for preventing overlapping until userspace program launched.
And, launched program continually dump out the trace buffer for later
analysis and it would change system behaviour with more possibility rather
than just keeping it in memory, so bad for debug.
Moreover, we can use page_owner feature further for various purposes. For
example, we can use it for fragmentation statistics implemented in this
patch. And, I also plan to implement some CMA failure debugging feature
using this interface.
I'd like to give the credit for all developers contributed this feature,
but, it's not easy because I don't know exact history. Sorry about that.
Below is people who has "Signed-off-by" in the patches in Andrew's tree.
Contributor:
Alexander Nyberg <alexn@dsv.su.se>
Mel Gorman <mgorman@suse.de>
Dave Hansen <dave@linux.vnet.ibm.com>
Minchan Kim <minchan@kernel.org>
Michal Nazarewicz <mina86@mina86.com>
Andrew Morton <akpm@linux-foundation.org>
Jungsoo Son <jungsoo.son@lge.com>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Mel Gorman <mgorman@suse.de>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Dave Hansen <dave@sr71.net>
Cc: Michal Nazarewicz <mina86@mina86.com>
Cc: Jungsoo Son <jungsoo.son@lge.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-12-13 08:56:01 +08:00
|
|
|
config PAGE_OWNER
|
|
|
|
bool "Track page owner"
|
|
|
|
depends on DEBUG_KERNEL && STACKTRACE_SUPPORT
|
|
|
|
select DEBUG_FS
|
|
|
|
select STACKTRACE
|
mm/page_owner: use stackdepot to store stacktrace
Currently, we store each page's allocation stacktrace on corresponding
page_ext structure and it requires a lot of memory. This causes the
problem that memory tight system doesn't work well if page_owner is
enabled. Moreover, even with this large memory consumption, we cannot
get full stacktrace because we allocate memory at boot time and just
maintain 8 stacktrace slots to balance memory consumption. We could
increase it to more but it would make system unusable or change system
behaviour.
To solve the problem, this patch uses stackdepot to store stacktrace.
It obviously provides memory saving but there is a drawback that
stackdepot could fail.
stackdepot allocates memory at runtime so it could fail if system has
not enough memory. But, most of allocation stack are generated at very
early time and there are much memory at this time. So, failure would
not happen easily. And, one failure means that we miss just one page's
allocation stacktrace so it would not be a big problem. In this patch,
when memory allocation failure happens, we store special stracktrace
handle to the page that is failed to save stacktrace. With it, user can
guess memory usage properly even if failure happens.
Memory saving looks as following. (4GB memory system with page_owner)
(before the patch -> after the patch)
static allocation:
92274688 bytes -> 25165824 bytes
dynamic allocation after boot + kernel build:
0 bytes -> 327680 bytes
total:
92274688 bytes -> 25493504 bytes
72% reduction in total.
Note that implementation looks complex than someone would imagine
because there is recursion issue. stackdepot uses page allocator and
page_owner is called at page allocation. Using stackdepot in page_owner
could re-call page allcator and then page_owner. That is a recursion.
To detect and avoid it, whenever we obtain stacktrace, recursion is
checked and page_owner is set to dummy information if found. Dummy
information means that this page is allocated for page_owner feature
itself (such as stackdepot) and it's understandable behavior for user.
[iamjoonsoo.kim@lge.com: mm-page_owner-use-stackdepot-to-store-stacktrace-v3]
Link: http://lkml.kernel.org/r/1464230275-25791-6-git-send-email-iamjoonsoo.kim@lge.com
Link: http://lkml.kernel.org/r/1466150259-27727-7-git-send-email-iamjoonsoo.kim@lge.com
Link: http://lkml.kernel.org/r/1464230275-25791-6-git-send-email-iamjoonsoo.kim@lge.com
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Mel Gorman <mgorman@techsingularity.net>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Alexander Potapenko <glider@google.com>
Cc: Hugh Dickins <hughd@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-07-27 06:23:55 +08:00
|
|
|
select STACKDEPOT
|
mm/page_owner: keep track of page owners
This is the page owner tracking code which is introduced so far ago. It
is resident on Andrew's tree, though, nobody tried to upstream so it
remain as is. Our company uses this feature actively to debug memory leak
or to find a memory hogger so I decide to upstream this feature.
This functionality help us to know who allocates the page. When
allocating a page, we store some information about allocation in extra
memory. Later, if we need to know status of all pages, we can get and
analyze it from this stored information.
In previous version of this feature, extra memory is statically defined in
struct page, but, in this version, extra memory is allocated outside of
struct page. It enables us to turn on/off this feature at boottime
without considerable memory waste.
Although we already have tracepoint for tracing page allocation/free,
using it to analyze page owner is rather complex. We need to enlarge the
trace buffer for preventing overlapping until userspace program launched.
And, launched program continually dump out the trace buffer for later
analysis and it would change system behaviour with more possibility rather
than just keeping it in memory, so bad for debug.
Moreover, we can use page_owner feature further for various purposes. For
example, we can use it for fragmentation statistics implemented in this
patch. And, I also plan to implement some CMA failure debugging feature
using this interface.
I'd like to give the credit for all developers contributed this feature,
but, it's not easy because I don't know exact history. Sorry about that.
Below is people who has "Signed-off-by" in the patches in Andrew's tree.
Contributor:
Alexander Nyberg <alexn@dsv.su.se>
Mel Gorman <mgorman@suse.de>
Dave Hansen <dave@linux.vnet.ibm.com>
Minchan Kim <minchan@kernel.org>
Michal Nazarewicz <mina86@mina86.com>
Andrew Morton <akpm@linux-foundation.org>
Jungsoo Son <jungsoo.son@lge.com>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Mel Gorman <mgorman@suse.de>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Dave Hansen <dave@sr71.net>
Cc: Michal Nazarewicz <mina86@mina86.com>
Cc: Jungsoo Son <jungsoo.son@lge.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-12-13 08:56:01 +08:00
|
|
|
select PAGE_EXTENSION
|
|
|
|
help
|
|
|
|
This keeps track of what call chain is the owner of a page, may
|
|
|
|
help to find bare alloc_page(s) leaks. Even if you include this
|
|
|
|
feature on your build, it is disabled in default. You should pass
|
|
|
|
"page_owner=on" to boot parameter in order to enable it. Eats
|
|
|
|
a fair amount of memory if enabled. See tools/vm/page_owner_sort.c
|
|
|
|
for user-space helper.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2006-12-10 18:18:37 +08:00
|
|
|
config DEBUG_FS
|
|
|
|
bool "Debug Filesystem"
|
debugfs: prevent access to possibly dead file_operations at file open
Nothing prevents a dentry found by path lookup before a return of
__debugfs_remove() to actually get opened after that return. Now, after
the return of __debugfs_remove(), there are no guarantees whatsoever
regarding the memory the corresponding inode's file_operations object
had been kept in.
Since __debugfs_remove() is seldomly invoked, usually from module exit
handlers only, the race is hard to trigger and the impact is very low.
A discussion of the problem outlined above as well as a suggested
solution can be found in the (sub-)thread rooted at
http://lkml.kernel.org/g/20130401203445.GA20862@ZenIV.linux.org.uk
("Yet another pipe related oops.")
Basically, Greg KH suggests to introduce an intermediate fops and
Al Viro points out that a pointer to the original ones may be stored in
->d_fsdata.
Follow this line of reasoning:
- Add SRCU as a reverse dependency of DEBUG_FS.
- Introduce a srcu_struct object for the debugfs subsystem.
- In debugfs_create_file(), store a pointer to the original
file_operations object in ->d_fsdata.
- Make debugfs_remove() and debugfs_remove_recursive() wait for a
SRCU grace period after the dentry has been delete()'d and before they
return to their callers.
- Introduce an intermediate file_operations object named
"debugfs_open_proxy_file_operations". It's ->open() functions checks,
under the protection of a SRCU read lock, whether the dentry is still
alive, i.e. has not been d_delete()'d and if so, tries to acquire a
reference on the owning module.
On success, it sets the file object's ->f_op to the original
file_operations and forwards the ongoing open() call to the original
->open().
- For clarity, rename the former debugfs_file_operations to
debugfs_noop_file_operations -- they are in no way canonical.
The choice of SRCU over "normal" RCU is justified by the fact, that the
former may also be used to protect ->i_private data from going away
during the execution of a file's readers and writers which may (and do)
sleep.
Finally, introduce the fs/debugfs/internal.h header containing some
declarations internal to the debugfs implementation.
Signed-off-by: Nicolai Stange <nicstange@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-03-22 21:11:13 +08:00
|
|
|
select SRCU
|
2006-12-10 18:18:37 +08:00
|
|
|
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.
|
|
|
|
|
2008-05-20 06:06:00 +08:00
|
|
|
For detailed documentation on the debugfs API, see
|
|
|
|
Documentation/DocBook/filesystems.
|
|
|
|
|
2006-12-10 18:18:37 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config HEADERS_CHECK
|
|
|
|
bool "Run 'make headers_check' when building vmlinux"
|
|
|
|
depends on !UML
|
|
|
|
help
|
|
|
|
This option will extract the user-visible kernel headers whenever
|
|
|
|
building the kernel, and will run basic sanity checks on them to
|
|
|
|
ensure that exported files do not attempt to include files which
|
|
|
|
were not exported, etc.
|
|
|
|
|
|
|
|
If you're making modifications to header files which are
|
|
|
|
relevant for userspace, say 'Y', and check the headers
|
|
|
|
exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
|
|
|
|
your build tree), to make sure they're suitable.
|
|
|
|
|
2008-01-22 04:31:44 +08:00
|
|
|
config DEBUG_SECTION_MISMATCH
|
|
|
|
bool "Enable full Section mismatch analysis"
|
|
|
|
help
|
|
|
|
The section mismatch analysis checks if there are illegal
|
|
|
|
references from one section to another section.
|
2011-04-17 12:08:48 +08:00
|
|
|
During linktime or runtime, some sections are dropped;
|
|
|
|
any use of code/data previously in these sections would
|
2008-01-22 04:31:44 +08:00
|
|
|
most likely result in an oops.
|
2011-04-17 12:08:48 +08:00
|
|
|
In the code, functions and variables are annotated with
|
2013-06-20 02:53:51 +08:00
|
|
|
__init,, etc. (see the full list in include/linux/init.h),
|
2008-01-30 18:13:23 +08:00
|
|
|
which results in the code/data being placed in specific sections.
|
2011-04-17 12:08:48 +08:00
|
|
|
The section mismatch analysis is always performed after a full
|
|
|
|
kernel build, and enabling this option causes the following
|
|
|
|
additional steps to occur:
|
|
|
|
- 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
|
2008-01-22 04:31:44 +08:00
|
|
|
the analysis would not catch the illegal reference.
|
2011-04-17 12:08:48 +08:00
|
|
|
This option tells gcc to inline less (but it does result in
|
|
|
|
a larger kernel).
|
|
|
|
- Run the section mismatch analysis for each module/built-in.o file.
|
|
|
|
When we run the section mismatch analysis on vmlinux.o, we
|
2016-09-09 16:04:58 +08:00
|
|
|
lose valuable information about where the mismatch was
|
2008-01-22 04:31:44 +08:00
|
|
|
introduced.
|
|
|
|
Running the analysis for each module/built-in.o file
|
2011-04-17 12:08:48 +08:00
|
|
|
tells where the mismatch happens much closer to the
|
|
|
|
source. The drawback is that the same mismatch is
|
|
|
|
reported at least twice.
|
|
|
|
- Enable verbose reporting from modpost in order to help resolve
|
|
|
|
the section mismatches that are reported.
|
2008-01-22 04:31:44 +08:00
|
|
|
|
2015-10-06 07:14:42 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
#
|
|
|
|
# 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
|
2006-01-10 12:54:51 +08:00
|
|
|
help
|
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
config FRAME_POINTER
|
|
|
|
bool "Compile the kernel with frame pointers"
|
|
|
|
depends on DEBUG_KERNEL && \
|
|
|
|
(CRIS || M68K || FRV || UML || \
|
|
|
|
AVR32 || SUPERH || BLACKFIN || MN10300 || METAG) || \
|
|
|
|
ARCH_WANT_FRAME_POINTERS
|
|
|
|
default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
|
2007-02-12 16:52:00 +08:00
|
|
|
help
|
2013-07-02 04:04:46 +08:00
|
|
|
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)
|
2007-02-12 16:52:00 +08:00
|
|
|
|
2016-02-29 12:22:42 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
For more information, see
|
|
|
|
tools/objtool/Documentation/stack-validation.txt.
|
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
config DEBUG_FORCE_WEAK_PER_CPU
|
|
|
|
bool "Force weak per-cpu definitions"
|
|
|
|
depends on DEBUG_KERNEL
|
2005-09-07 06:16:27 +08:00
|
|
|
help
|
2013-07-02 04:04:46 +08:00
|
|
|
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.
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
1. percpu symbols must be unique whether static or not
|
|
|
|
2. percpu variables can't be defined inside a function
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
To ensure that generic code follows the above rules, this
|
|
|
|
option forces all percpu variables to be defined as weak.
|
2012-02-10 06:42:21 +08:00
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
endmenu # "Compiler options"
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2013-07-02 04:04:46 +08:00
|
|
|
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
|
|
|
|
keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
|
|
|
|
unless you really know what this hack does.
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2013-10-07 08:05:46 +08:00
|
|
|
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
|
|
|
|
to a bitmask as described in Documentation/sysrq.txt.
|
|
|
|
|
2006-01-10 12:54:51 +08:00
|
|
|
config DEBUG_KERNEL
|
|
|
|
bool "Kernel debugging"
|
2011-03-23 07:34:16 +08:00
|
|
|
help
|
2006-01-10 12:54:51 +08:00
|
|
|
Say Y here if you are developing drivers or trying to debug and
|
|
|
|
identify kernel problems.
|
2011-03-23 07:34:16 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
menu "Memory Debugging"
|
2011-03-23 07:34:16 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
source mm/Kconfig.debug
|
2011-03-23 07:34:16 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config DEBUG_OBJECTS
|
|
|
|
bool "Debug object operations"
|
|
|
|
depends on DEBUG_KERNEL
|
2008-05-13 03:21:04 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2008-05-13 03:21:04 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config DEBUG_OBJECTS_SELFTEST
|
|
|
|
bool "Debug objects selftest"
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
help
|
|
|
|
This enables the selftest of the object debug code.
|
2008-05-13 03:21:04 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2008-04-30 15:55:01 +08:00
|
|
|
|
2008-04-30 15:55:03 +08:00
|
|
|
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.
|
|
|
|
|
2009-11-16 00:09:48 +08:00
|
|
|
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.
|
|
|
|
|
2010-04-17 20:48:42 +08:00
|
|
|
config DEBUG_OBJECTS_RCU_HEAD
|
|
|
|
bool "Debug RCU callbacks objects"
|
2011-02-24 01:42:14 +08:00
|
|
|
depends on DEBUG_OBJECTS
|
2010-04-17 20:48:42 +08:00
|
|
|
help
|
|
|
|
Enable this to turn on debugging of RCU list heads (call_rcu() usage).
|
|
|
|
|
2010-10-27 05:23:05 +08:00
|
|
|
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.
|
|
|
|
|
2008-11-26 17:02:00 +08:00
|
|
|
config DEBUG_OBJECTS_ENABLE_DEFAULT
|
|
|
|
int "debug_objects bootup default value (0-1)"
|
|
|
|
range 0 1
|
|
|
|
default "1"
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
help
|
|
|
|
Debug objects boot parameter default value
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_SLAB
|
2006-03-25 19:07:22 +08:00
|
|
|
bool "Debug slab memory allocations"
|
2008-04-04 06:51:41 +08:00
|
|
|
depends on DEBUG_KERNEL && SLAB && !KMEMCHECK
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
2006-03-25 19:06:39 +08:00
|
|
|
config DEBUG_SLAB_LEAK
|
|
|
|
bool "Memory leak debugging"
|
|
|
|
depends on DEBUG_SLAB
|
|
|
|
|
2007-07-16 14:38:14 +08:00
|
|
|
config SLUB_DEBUG_ON
|
|
|
|
bool "SLUB debugging on by default"
|
2008-04-04 06:51:41 +08:00
|
|
|
depends on SLUB && SLUB_DEBUG && !KMEMCHECK
|
2007-07-16 14:38:14 +08:00
|
|
|
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=-".
|
|
|
|
|
2008-02-08 09:47:41 +08:00
|
|
|
config SLUB_STATS
|
|
|
|
default n
|
|
|
|
bool "Enable SLUB performance statistics"
|
2010-10-06 02:57:26 +08:00
|
|
|
depends on SLUB && SYSFS
|
2008-02-08 09:47:41 +08:00
|
|
|
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
|
|
|
|
|
2012-10-09 07:28:11 +08:00
|
|
|
config HAVE_DEBUG_KMEMLEAK
|
|
|
|
bool
|
|
|
|
|
2009-06-11 20:24:13 +08:00
|
|
|
config DEBUG_KMEMLEAK
|
|
|
|
bool "Kernel memory leak detector"
|
2013-01-17 10:54:16 +08:00
|
|
|
depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK
|
2011-04-28 00:06:19 +08:00
|
|
|
select DEBUG_FS
|
2009-06-11 20:24:13 +08:00
|
|
|
select STACKTRACE if STACKTRACE_SUPPORT
|
|
|
|
select KALLSYMS
|
2009-11-07 07:33:45 +08:00
|
|
|
select CRC32
|
2009-06-11 20:24:13 +08:00
|
|
|
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
|
|
|
|
allocations. See Documentation/kmemleak.txt for more
|
|
|
|
details.
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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).
|
|
|
|
|
|
|
|
config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
|
|
|
|
int "Maximum kmemleak early log entries"
|
|
|
|
depends on DEBUG_KMEMLEAK
|
|
|
|
range 200 40000
|
|
|
|
default 400
|
|
|
|
help
|
|
|
|
Kmemleak must track all the memory allocations to avoid
|
|
|
|
reporting false positives. Since memory may be allocated or
|
|
|
|
freed before kmemleak is initialised, an early log buffer is
|
|
|
|
used to store these actions. If kmemleak reports "early log
|
|
|
|
buffer exceeded", please increase this value.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
config DEBUG_STACK_USAGE
|
|
|
|
bool "Stack utilization instrumentation"
|
2016-03-20 00:54:10 +08:00
|
|
|
depends on DEBUG_KERNEL && !IA64
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
config DEBUG_VM
|
|
|
|
bool "Debug VM"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Enable this to turn on extended checks in the virtual-memory system
|
|
|
|
that may impact performance.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2014-06-05 07:06:46 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config DEBUG_VM_RB
|
|
|
|
bool "Debug VM red-black trees"
|
|
|
|
depends on DEBUG_VM
|
|
|
|
help
|
2014-04-19 06:07:22 +08:00
|
|
|
Enable VM red-black tree debugging information and extra validations.
|
2013-07-02 04:04:43 +08:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2016-01-16 08:51:21 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config DEBUG_VIRTUAL
|
|
|
|
bool "Debug VM translations"
|
|
|
|
depends on DEBUG_KERNEL && X86
|
|
|
|
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.
|
|
|
|
|
|
|
|
config DEBUG_HIGHMEM
|
|
|
|
bool "Highmem debugging"
|
|
|
|
depends on DEBUG_KERNEL && HIGHMEM
|
|
|
|
help
|
2014-04-15 00:55:50 +08:00
|
|
|
This option enables additional error checking for high memory
|
|
|
|
systems. Disable for production systems.
|
2013-07-02 04:04:43 +08:00
|
|
|
|
|
|
|
config HAVE_DEBUG_STACKOVERFLOW
|
|
|
|
bool
|
|
|
|
|
|
|
|
config DEBUG_STACKOVERFLOW
|
|
|
|
bool "Check for stack overflows"
|
|
|
|
depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW
|
|
|
|
---help---
|
|
|
|
Say Y here if you want to check for overflows of kernel, IRQ
|
2015-01-26 02:50:34 +08:00
|
|
|
and exception stacks (if your architecture uses them). This
|
2013-07-02 04:04:43 +08:00
|
|
|
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".
|
|
|
|
|
|
|
|
source "lib/Kconfig.kmemcheck"
|
|
|
|
|
kasan: add kernel address sanitizer infrastructure
Kernel Address sanitizer (KASan) is a dynamic memory error detector. It
provides fast and comprehensive solution for finding use-after-free and
out-of-bounds bugs.
KASAN uses compile-time instrumentation for checking every memory access,
therefore GCC > v4.9.2 required. v4.9.2 almost works, but has issues with
putting symbol aliases into the wrong section, which breaks kasan
instrumentation of globals.
This patch only adds infrastructure for kernel address sanitizer. It's
not available for use yet. The idea and some code was borrowed from [1].
Basic idea:
The main idea of KASAN is to use shadow memory to record whether each byte
of memory is safe to access or not, and use compiler's instrumentation to
check the shadow memory on each memory access.
Address sanitizer uses 1/8 of the memory addressable in kernel for shadow
memory and uses direct mapping with a scale and offset to translate a
memory address to its corresponding shadow address.
Here is function to translate address to corresponding shadow address:
unsigned long kasan_mem_to_shadow(unsigned long addr)
{
return (addr >> KASAN_SHADOW_SCALE_SHIFT) + KASAN_SHADOW_OFFSET;
}
where KASAN_SHADOW_SCALE_SHIFT = 3.
So for every 8 bytes there is one corresponding byte of shadow memory.
The following encoding used for each shadow byte: 0 means that all 8 bytes
of the corresponding memory region are valid for access; k (1 <= k <= 7)
means that the first k bytes are valid for access, and other (8 - k) bytes
are not; Any negative value indicates that the entire 8-bytes are
inaccessible. Different negative values used to distinguish between
different kinds of inaccessible memory (redzones, freed memory) (see
mm/kasan/kasan.h).
To be able to detect accesses to bad memory we need a special compiler.
Such compiler inserts a specific function calls (__asan_load*(addr),
__asan_store*(addr)) before each memory access of size 1, 2, 4, 8 or 16.
These functions check whether memory region is valid to access or not by
checking corresponding shadow memory. If access is not valid an error
printed.
Historical background of the address sanitizer from Dmitry Vyukov:
"We've developed the set of tools, AddressSanitizer (Asan),
ThreadSanitizer and MemorySanitizer, for user space. We actively use
them for testing inside of Google (continuous testing, fuzzing,
running prod services). To date the tools have found more than 10'000
scary bugs in Chromium, Google internal codebase and various
open-source projects (Firefox, OpenSSL, gcc, clang, ffmpeg, MySQL and
lots of others): [2] [3] [4].
The tools are part of both gcc and clang compilers.
We have not yet done massive testing under the Kernel AddressSanitizer
(it's kind of chicken and egg problem, you need it to be upstream to
start applying it extensively). To date it has found about 50 bugs.
Bugs that we've found in upstream kernel are listed in [5].
We've also found ~20 bugs in out internal version of the kernel. Also
people from Samsung and Oracle have found some.
[...]
As others noted, the main feature of AddressSanitizer is its
performance due to inline compiler instrumentation and simple linear
shadow memory. User-space Asan has ~2x slowdown on computational
programs and ~2x memory consumption increase. Taking into account that
kernel usually consumes only small fraction of CPU and memory when
running real user-space programs, I would expect that kernel Asan will
have ~10-30% slowdown and similar memory consumption increase (when we
finish all tuning).
I agree that Asan can well replace kmemcheck. We have plans to start
working on Kernel MemorySanitizer that finds uses of unitialized
memory. Asan+Msan will provide feature-parity with kmemcheck. As
others noted, Asan will unlikely replace debug slab and pagealloc that
can be enabled at runtime. Asan uses compiler instrumentation, so even
if it is disabled, it still incurs visible overheads.
Asan technology is easily portable to other architectures. Compiler
instrumentation is fully portable. Runtime has some arch-dependent
parts like shadow mapping and atomic operation interception. They are
relatively easy to port."
Comparison with other debugging features:
========================================
KMEMCHECK:
- KASan can do almost everything that kmemcheck can. KASan uses
compile-time instrumentation, which makes it significantly faster than
kmemcheck. The only advantage of kmemcheck over KASan is detection of
uninitialized memory reads.
Some brief performance testing showed that kasan could be
x500-x600 times faster than kmemcheck:
$ netperf -l 30
MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to localhost (127.0.0.1) port 0 AF_INET
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
no debug: 87380 16384 16384 30.00 41624.72
kasan inline: 87380 16384 16384 30.00 12870.54
kasan outline: 87380 16384 16384 30.00 10586.39
kmemcheck: 87380 16384 16384 30.03 20.23
- Also kmemcheck couldn't work on several CPUs. It always sets
number of CPUs to 1. KASan doesn't have such limitation.
DEBUG_PAGEALLOC:
- KASan is slower than DEBUG_PAGEALLOC, but KASan works on sub-page
granularity level, so it able to find more bugs.
SLUB_DEBUG (poisoning, redzones):
- SLUB_DEBUG has lower overhead than KASan.
- SLUB_DEBUG in most cases are not able to detect bad reads,
KASan able to detect both reads and writes.
- In some cases (e.g. redzone overwritten) SLUB_DEBUG detect
bugs only on allocation/freeing of object. KASan catch
bugs right before it will happen, so we always know exact
place of first bad read/write.
[1] https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel
[2] https://code.google.com/p/address-sanitizer/wiki/FoundBugs
[3] https://code.google.com/p/thread-sanitizer/wiki/FoundBugs
[4] https://code.google.com/p/memory-sanitizer/wiki/FoundBugs
[5] https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel#Trophies
Based on work by Andrey Konovalov.
Signed-off-by: Andrey Ryabinin <a.ryabinin@samsung.com>
Acked-by: Michal Marek <mmarek@suse.cz>
Signed-off-by: Andrey Konovalov <adech.fo@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Konstantin Serebryany <kcc@google.com>
Cc: Dmitry Chernenkov <dmitryc@google.com>
Cc: Yuri Gribov <tetra2005@gmail.com>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: David Rientjes <rientjes@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2015-02-14 06:39:17 +08:00
|
|
|
source "lib/Kconfig.kasan"
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
endmenu # "Memory Debugging"
|
|
|
|
|
kernel: add kcov code coverage
kcov provides code coverage collection for coverage-guided fuzzing
(randomized testing). Coverage-guided fuzzing is a testing technique
that uses coverage feedback to determine new interesting inputs to a
system. A notable user-space example is AFL
(http://lcamtuf.coredump.cx/afl/). However, this technique is not
widely used for kernel testing due to missing compiler and kernel
support.
kcov does not aim to collect as much coverage as possible. It aims to
collect more or less stable coverage that is function of syscall inputs.
To achieve this goal it does not collect coverage in soft/hard
interrupts and instrumentation of some inherently non-deterministic or
non-interesting parts of kernel is disbled (e.g. scheduler, locking).
Currently there is a single coverage collection mode (tracing), but the
API anticipates additional collection modes. Initially I also
implemented a second mode which exposes coverage in a fixed-size hash
table of counters (what Quentin used in his original patch). I've
dropped the second mode for simplicity.
This patch adds the necessary support on kernel side. The complimentary
compiler support was added in gcc revision 231296.
We've used this support to build syzkaller system call fuzzer, which has
found 90 kernel bugs in just 2 months:
https://github.com/google/syzkaller/wiki/Found-Bugs
We've also found 30+ bugs in our internal systems with syzkaller.
Another (yet unexplored) direction where kcov coverage would greatly
help is more traditional "blob mutation". For example, mounting a
random blob as a filesystem, or receiving a random blob over wire.
Why not gcov. Typical fuzzing loop looks as follows: (1) reset
coverage, (2) execute a bit of code, (3) collect coverage, repeat. A
typical coverage can be just a dozen of basic blocks (e.g. an invalid
input). In such context gcov becomes prohibitively expensive as
reset/collect coverage steps depend on total number of basic
blocks/edges in program (in case of kernel it is about 2M). Cost of
kcov depends only on number of executed basic blocks/edges. On top of
that, kernel requires per-thread coverage because there are always
background threads and unrelated processes that also produce coverage.
With inlined gcov instrumentation per-thread coverage is not possible.
kcov exposes kernel PCs and control flow to user-space which is
insecure. But debugfs should not be mapped as user accessible.
Based on a patch by Quentin Casasnovas.
[akpm@linux-foundation.org: make task_struct.kcov_mode have type `enum kcov_mode']
[akpm@linux-foundation.org: unbreak allmodconfig]
[akpm@linux-foundation.org: follow x86 Makefile layout standards]
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Cc: syzkaller <syzkaller@googlegroups.com>
Cc: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Tavis Ormandy <taviso@google.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com>
Cc: Kostya Serebryany <kcc@google.com>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Kees Cook <keescook@google.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: David Drysdale <drysdale@google.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Kirill A. Shutemov <kirill@shutemov.name>
Cc: Jiri Slaby <jslaby@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-23 05:27:30 +08:00
|
|
|
config ARCH_HAS_KCOV
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
KCOV does not have any arch-specific code, but currently it is enabled
|
|
|
|
only for x86_64. KCOV requires testing on other archs, and most likely
|
|
|
|
disabling of instrumentation for some early boot code.
|
|
|
|
|
|
|
|
config KCOV
|
|
|
|
bool "Code coverage for fuzzing"
|
|
|
|
depends on ARCH_HAS_KCOV
|
|
|
|
select DEBUG_FS
|
2016-06-12 00:09:28 +08:00
|
|
|
select GCC_PLUGINS if !COMPILE_TEST
|
|
|
|
select GCC_PLUGIN_SANCOV if !COMPILE_TEST
|
kernel: add kcov code coverage
kcov provides code coverage collection for coverage-guided fuzzing
(randomized testing). Coverage-guided fuzzing is a testing technique
that uses coverage feedback to determine new interesting inputs to a
system. A notable user-space example is AFL
(http://lcamtuf.coredump.cx/afl/). However, this technique is not
widely used for kernel testing due to missing compiler and kernel
support.
kcov does not aim to collect as much coverage as possible. It aims to
collect more or less stable coverage that is function of syscall inputs.
To achieve this goal it does not collect coverage in soft/hard
interrupts and instrumentation of some inherently non-deterministic or
non-interesting parts of kernel is disbled (e.g. scheduler, locking).
Currently there is a single coverage collection mode (tracing), but the
API anticipates additional collection modes. Initially I also
implemented a second mode which exposes coverage in a fixed-size hash
table of counters (what Quentin used in his original patch). I've
dropped the second mode for simplicity.
This patch adds the necessary support on kernel side. The complimentary
compiler support was added in gcc revision 231296.
We've used this support to build syzkaller system call fuzzer, which has
found 90 kernel bugs in just 2 months:
https://github.com/google/syzkaller/wiki/Found-Bugs
We've also found 30+ bugs in our internal systems with syzkaller.
Another (yet unexplored) direction where kcov coverage would greatly
help is more traditional "blob mutation". For example, mounting a
random blob as a filesystem, or receiving a random blob over wire.
Why not gcov. Typical fuzzing loop looks as follows: (1) reset
coverage, (2) execute a bit of code, (3) collect coverage, repeat. A
typical coverage can be just a dozen of basic blocks (e.g. an invalid
input). In such context gcov becomes prohibitively expensive as
reset/collect coverage steps depend on total number of basic
blocks/edges in program (in case of kernel it is about 2M). Cost of
kcov depends only on number of executed basic blocks/edges. On top of
that, kernel requires per-thread coverage because there are always
background threads and unrelated processes that also produce coverage.
With inlined gcov instrumentation per-thread coverage is not possible.
kcov exposes kernel PCs and control flow to user-space which is
insecure. But debugfs should not be mapped as user accessible.
Based on a patch by Quentin Casasnovas.
[akpm@linux-foundation.org: make task_struct.kcov_mode have type `enum kcov_mode']
[akpm@linux-foundation.org: unbreak allmodconfig]
[akpm@linux-foundation.org: follow x86 Makefile layout standards]
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Cc: syzkaller <syzkaller@googlegroups.com>
Cc: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Tavis Ormandy <taviso@google.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com>
Cc: Kostya Serebryany <kcc@google.com>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Kees Cook <keescook@google.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: David Drysdale <drysdale@google.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Kirill A. Shutemov <kirill@shutemov.name>
Cc: Jiri Slaby <jslaby@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-23 05:27:30 +08:00
|
|
|
help
|
|
|
|
KCOV exposes kernel code coverage information in a form suitable
|
|
|
|
for coverage-guided fuzzing (randomized testing).
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
For more details, see Documentation/kcov.txt.
|
|
|
|
|
2016-08-03 05:07:30 +08:00
|
|
|
config KCOV_INSTRUMENT_ALL
|
|
|
|
bool "Instrument all code by default"
|
|
|
|
depends on KCOV
|
|
|
|
default y if KCOV
|
|
|
|
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.
|
|
|
|
|
2007-02-12 16:52:00 +08:00
|
|
|
config DEBUG_SHIRQ
|
|
|
|
bool "Debug shared IRQ handlers"
|
2013-08-30 15:39:53 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2007-02-12 16:52:00 +08:00
|
|
|
help
|
|
|
|
Enable this to generate a spurious interrupt as soon as a shared
|
|
|
|
interrupt handler is registered, and just before one is deregistered.
|
|
|
|
Drivers ought to be able to handle interrupts coming in at those
|
|
|
|
points; some don't and need to be caught.
|
|
|
|
|
2013-07-02 04:04:50 +08:00
|
|
|
menu "Debug Lockups and Hangs"
|
|
|
|
|
2010-05-08 05:11:44 +08:00
|
|
|
config LOCKUP_DETECTOR
|
|
|
|
bool "Detect Hard and Soft Lockups"
|
2006-10-11 16:20:44 +08:00
|
|
|
depends on DEBUG_KERNEL && !S390
|
2005-09-07 06:16:27 +08:00
|
|
|
help
|
2010-05-08 05:11:44 +08:00
|
|
|
Say Y here to enable the kernel to act as a watchdog to detect
|
|
|
|
hard and soft lockups.
|
|
|
|
|
|
|
|
Softlockups are bugs that cause the kernel to loop in kernel
|
2012-02-10 06:42:21 +08:00
|
|
|
mode for more than 20 seconds, without giving other tasks a
|
2010-05-08 05:11:44 +08:00
|
|
|
chance to run. The current stack trace is displayed upon
|
|
|
|
detection and the system will stay locked up.
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2010-05-08 05:11:44 +08:00
|
|
|
Hardlockups are bugs that cause the CPU to loop in kernel mode
|
2012-02-10 06:42:21 +08:00
|
|
|
for more than 10 seconds, without letting other interrupts have a
|
2010-05-08 05:11:44 +08:00
|
|
|
chance to run. The current stack trace is displayed upon detection
|
|
|
|
and the system will stay locked up.
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2010-05-08 05:11:44 +08:00
|
|
|
The overhead should be minimal. A periodic hrtimer runs to
|
2012-02-10 06:42:21 +08:00
|
|
|
generate interrupts and kick the watchdog task every 4 seconds.
|
|
|
|
An NMI is generated every 10 seconds or so to check for hardlockups.
|
|
|
|
|
|
|
|
The frequency of hrtimer and NMI events and the soft and hard lockup
|
|
|
|
thresholds can be controlled through the sysctl watchdog_thresh.
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2010-05-16 05:15:20 +08:00
|
|
|
config HARDLOCKUP_DETECTOR
|
2012-10-05 08:13:17 +08:00
|
|
|
def_bool y
|
|
|
|
depends on LOCKUP_DETECTOR && !HAVE_NMI_WATCHDOG
|
|
|
|
depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
|
2005-09-07 06:16:27 +08:00
|
|
|
|
2011-03-23 07:34:16 +08:00
|
|
|
config BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
bool "Panic (Reboot) On Hard Lockups"
|
2012-10-05 08:13:17 +08:00
|
|
|
depends on HARDLOCKUP_DETECTOR
|
2011-03-23 07:34:16 +08:00
|
|
|
help
|
|
|
|
Say Y here to enable the kernel to panic on "hard lockups",
|
|
|
|
which are bugs that cause the kernel to loop in kernel
|
2012-02-10 06:42:21 +08:00
|
|
|
mode with interrupts disabled for more than 10 seconds (configurable
|
|
|
|
using the watchdog_thresh sysctl).
|
2011-03-23 07:34:16 +08:00
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
config BOOTPARAM_HARDLOCKUP_PANIC_VALUE
|
|
|
|
int
|
2012-10-05 08:13:17 +08:00
|
|
|
depends on HARDLOCKUP_DETECTOR
|
2011-03-23 07:34:16 +08:00
|
|
|
range 0 1
|
|
|
|
default 0 if !BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
default 1 if BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
|
2008-05-13 03:21:04 +08:00
|
|
|
config BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
bool "Panic (Reboot) On Soft Lockups"
|
2010-05-13 06:27:20 +08:00
|
|
|
depends on LOCKUP_DETECTOR
|
2008-05-13 03:21:04 +08:00
|
|
|
help
|
|
|
|
Say Y here to enable the kernel to panic on "soft lockups",
|
|
|
|
which are bugs that cause the kernel to loop in kernel
|
2012-02-10 06:42:21 +08:00
|
|
|
mode for more than 20 seconds (configurable using the watchdog_thresh
|
|
|
|
sysctl), without giving other tasks a chance to run.
|
2008-05-13 03:21:04 +08:00
|
|
|
|
|
|
|
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
|
2010-05-16 04:30:22 +08:00
|
|
|
depends on LOCKUP_DETECTOR
|
2008-05-13 03:21:04 +08:00
|
|
|
range 0 1
|
|
|
|
default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
default 1 if BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
|
2009-01-16 03:08:40 +08:00
|
|
|
config DETECT_HUNG_TASK
|
|
|
|
bool "Detect Hung Tasks"
|
|
|
|
depends on DEBUG_KERNEL
|
2011-07-05 11:32:40 +08:00
|
|
|
default LOCKUP_DETECTOR
|
2009-01-16 03:08:40 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
Say Y here to enable the kernel to detect "hung tasks",
|
|
|
|
which are bugs that cause the task to be stuck in
|
2016-09-23 04:55:13 +08:00
|
|
|
uninterruptible "D" state indefinitely.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2006-03-25 19:06:39 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config DEFAULT_HUNG_TASK_TIMEOUT
|
|
|
|
int "Default timeout for hung task detection (in seconds)"
|
|
|
|
depends on DETECT_HUNG_TASK
|
|
|
|
default 120
|
2007-07-16 14:38:14 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
This option controls the default timeout (in seconds) used
|
|
|
|
to determine when a task has become non-responsive and should
|
|
|
|
be considered hung.
|
2007-07-16 14:38:14 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2008-02-08 09:47:41 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
A timeout of 0 disables the check. The default is two minutes.
|
|
|
|
Keeping the default should be fine in most cases.
|
2012-10-09 07:28:11 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config BOOTPARAM_HUNG_TASK_PANIC
|
|
|
|
bool "Panic (Reboot) On Hung Tasks"
|
|
|
|
depends on DETECT_HUNG_TASK
|
2009-06-11 20:24:13 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2009-06-11 20:24:13 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2009-06-23 21:40:27 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
Say N if unsure.
|
2009-06-23 21:40:27 +08:00
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
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
|
2009-06-11 20:24:13 +08:00
|
|
|
|
workqueue: implement lockup detector
Workqueue stalls can happen from a variety of usage bugs such as
missing WQ_MEM_RECLAIM flag or concurrency managed work item
indefinitely staying RUNNING. These stalls can be extremely difficult
to hunt down because the usual warning mechanisms can't detect
workqueue stalls and the internal state is pretty opaque.
To alleviate the situation, this patch implements workqueue lockup
detector. It periodically monitors all worker_pools periodically and,
if any pool failed to make forward progress longer than the threshold
duration, triggers warning and dumps workqueue state as follows.
BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 31s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=17/256
pending: monkey_wrench_fn, e1000_watchdog, cache_reap, vmstat_shepherd, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, release_one_tty, cgroup_release_agent
workqueue events_power_efficient: flags=0x80
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
pending: check_lifetime, neigh_periodic_work
workqueue cgroup_pidlist_destroy: flags=0x0
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/1
pending: cgroup_pidlist_destroy_work_fn
...
The detection mechanism is controller through kernel parameter
workqueue.watchdog_thresh and can be updated at runtime through the
sysfs module parameter file.
v2: Decoupled from softlockup control knobs.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Don Zickus <dzickus@redhat.com>
Cc: Ulrich Obergfell <uobergfe@redhat.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Chris Mason <clm@fb.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
2015-12-09 00:28:04 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:50 +08:00
|
|
|
endmenu # "Debug lockups and hangs"
|
|
|
|
|
|
|
|
config PANIC_ON_OOPS
|
|
|
|
bool "Panic on Oops"
|
2009-06-25 17:16:11 +08:00
|
|
|
help
|
2013-07-02 04:04:50 +08:00
|
|
|
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.
|
2009-06-25 17:16:11 +08:00
|
|
|
|
2013-07-02 04:04:50 +08:00
|
|
|
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
|
|
|
|
|
2013-11-26 07:23:04 +08:00
|
|
|
config PANIC_TIMEOUT
|
|
|
|
int "panic timeout"
|
|
|
|
default 0
|
|
|
|
help
|
|
|
|
Set the timeout value (in seconds) until a reboot occurs when the
|
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config SCHED_DEBUG
|
|
|
|
bool "Collect scheduler debugging info"
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
|
|
|
default y
|
2009-06-11 20:24:14 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2009-06-11 20:24:14 +08:00
|
|
|
|
2015-06-26 02:23:37 +08:00
|
|
|
config SCHED_INFO
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config SCHEDSTATS
|
|
|
|
bool "Collect scheduler statistics"
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
2015-06-26 02:23:37 +08:00
|
|
|
select SCHED_INFO
|
2013-07-02 04:04:43 +08:00
|
|
|
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.
|
2009-06-11 20:24:14 +08:00
|
|
|
|
2014-09-12 21:16:19 +08:00
|
|
|
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.
|
|
|
|
|
2015-03-12 12:16:32 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:43 +08:00
|
|
|
config TIMER_STATS
|
|
|
|
bool "Collect kernel timers statistics"
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
2010-07-19 18:54:17 +08:00
|
|
|
help
|
2013-07-02 04:04:43 +08:00
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
timer routines to collect statistics about kernel timers being
|
|
|
|
reprogrammed. The statistics can be read from /proc/timer_stats.
|
|
|
|
The statistics collection is started by writing 1 to /proc/timer_stats,
|
|
|
|
writing 0 stops it. This feature is useful to collect information
|
|
|
|
about timer usage patterns in kernel and userspace. This feature
|
|
|
|
is lightweight if enabled in the kernel config but not activated
|
|
|
|
(it defaults to deactivated on bootup and will only be activated
|
|
|
|
if some application like powertop activates it explicitly).
|
2010-07-19 18:54:17 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_PREEMPT
|
|
|
|
bool "Debug preemptible kernel"
|
2009-10-16 15:21:39 +08:00
|
|
|
depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:47 +08:00
|
|
|
menu "Lock Debugging (spinlocks, mutexes, etc...)"
|
|
|
|
|
2006-06-27 17:54:55 +08:00
|
|
|
config DEBUG_RT_MUTEXES
|
|
|
|
bool "RT Mutex debugging, deadlock detection"
|
|
|
|
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.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_SPINLOCK
|
2006-07-03 15:24:55 +08:00
|
|
|
bool "Spinlock and rw-lock debugging: basic checks"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2012-03-22 17:55:08 +08:00
|
|
|
select UNINLINE_SPIN_UNLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
2006-07-03 15:24:55 +08:00
|
|
|
config DEBUG_MUTEXES
|
|
|
|
bool "Mutex debugging: basic checks"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
This feature allows mutex semantics violations to be detected and
|
|
|
|
reported.
|
|
|
|
|
2013-06-20 19:31:17 +08:00
|
|
|
config DEBUG_WW_MUTEX_SLOWPATH
|
|
|
|
bool "Wait/wound mutex debugging: Slowpath testing"
|
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
|
|
|
select DEBUG_LOCK_ALLOC
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
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.
|
2014-08-27 23:19:26 +08:00
|
|
|
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.
|
2013-06-20 19:31:17 +08:00
|
|
|
|
2006-07-03 15:24:55 +08:00
|
|
|
config DEBUG_LOCK_ALLOC
|
|
|
|
bool "Lock debugging: detect incorrect freeing of live locks"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
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.
|
|
|
|
|
|
|
|
config PROVE_LOCKING
|
|
|
|
bool "Lock debugging: prove locking correctness"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select LOCKDEP
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
select DEBUG_LOCK_ALLOC
|
2010-09-01 04:35:20 +08:00
|
|
|
select TRACE_IRQFLAGS
|
2006-07-03 15:24:55 +08:00
|
|
|
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.
|
|
|
|
|
2014-07-31 04:41:55 +08:00
|
|
|
For more details, see Documentation/locking/lockdep-design.txt.
|
2006-07-03 15:24:55 +08:00
|
|
|
|
|
|
|
config LOCKDEP
|
|
|
|
bool
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select STACKTRACE
|
2014-06-24 04:22:04 +08:00
|
|
|
select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE && !ARC && !SCORE
|
2006-07-03 15:24:55 +08:00
|
|
|
select KALLSYMS
|
|
|
|
select KALLSYMS_ALL
|
|
|
|
|
2007-07-19 16:48:56 +08:00
|
|
|
config LOCK_STAT
|
2007-09-25 12:24:43 +08:00
|
|
|
bool "Lock usage statistics"
|
2007-07-19 16:48:56 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
|
|
|
select LOCKDEP
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
select DEBUG_LOCK_ALLOC
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This feature enables tracking lock contention points
|
|
|
|
|
2014-07-31 04:41:55 +08:00
|
|
|
For more details, see Documentation/locking/lockstat.txt
|
2007-10-07 15:24:33 +08:00
|
|
|
|
2010-02-28 00:10:39 +08:00
|
|
|
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.
|
2010-02-04 15:08:15 +08:00
|
|
|
|
|
|
|
CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
|
2010-02-28 00:10:39 +08:00
|
|
|
(CONFIG_LOCKDEP defines "acquire" and "release" events.)
|
2010-02-04 15:08:15 +08:00
|
|
|
|
2006-07-03 15:24:55 +08:00
|
|
|
config DEBUG_LOCKDEP
|
|
|
|
bool "Lock dependency engine debugging"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && LOCKDEP
|
2006-07-03 15:24:55 +08:00
|
|
|
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.
|
|
|
|
|
2011-06-09 01:31:56 +08:00
|
|
|
config DEBUG_ATOMIC_SLEEP
|
|
|
|
bool "Sleep inside atomic section checking"
|
2011-06-08 07:51:02 +08:00
|
|
|
select PREEMPT_COUNT
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
If you say Y here, various routines which may sleep will become very
|
2011-06-09 01:31:56 +08:00
|
|
|
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...
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-07-03 15:24:48 +08:00
|
|
|
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
|
|
|
|
lock debugging then those bugs wont be detected of course.)
|
|
|
|
The following locking APIs are covered: spinlocks, rwlocks,
|
|
|
|
mutexes and rwsems.
|
|
|
|
|
2014-02-05 07:51:41 +08:00
|
|
|
config LOCK_TORTURE_TEST
|
|
|
|
tristate "torture tests for locking"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
select TORTURE_TEST
|
|
|
|
default n
|
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:47 +08:00
|
|
|
endmenu # lock debugging
|
2006-07-03 15:24:38 +08:00
|
|
|
|
2013-07-02 04:04:47 +08:00
|
|
|
config TRACE_IRQFLAGS
|
|
|
|
bool
|
2011-05-25 08:13:36 +08:00
|
|
|
help
|
2013-07-02 04:04:47 +08:00
|
|
|
Enables hooks to interrupt enabling and disabling for
|
|
|
|
either tracing or lock debugging.
|
2011-05-25 08:13:36 +08:00
|
|
|
|
2006-07-03 15:24:38 +08:00
|
|
|
config STACKTRACE
|
2014-08-30 06:18:35 +08:00
|
|
|
bool "Stack backtrace support"
|
2006-07-03 15:24:38 +08:00
|
|
|
depends on STACKTRACE_SUPPORT
|
2014-08-30 06:18:35 +08:00
|
|
|
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.
|
2011-05-25 08:13:36 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_KOBJECT
|
|
|
|
bool "kobject debugging"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
If you say Y here, some extra kobject debugging messages will be sent
|
|
|
|
to the syslog.
|
|
|
|
|
2013-06-27 22:06:14 +08:00
|
|
|
config DEBUG_KOBJECT_RELEASE
|
|
|
|
bool "kobject release debugging"
|
2013-10-29 23:33:36 +08:00
|
|
|
depends on DEBUG_OBJECTS_TIMERS
|
2013-06-27 22:06:14 +08:00
|
|
|
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.
|
|
|
|
|
2012-10-09 07:28:13 +08:00
|
|
|
config HAVE_DEBUG_BUGVERBOSE
|
|
|
|
bool
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_BUGVERBOSE
|
2011-01-21 06:44:16 +08:00
|
|
|
bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
|
2012-10-09 07:28:13 +08:00
|
|
|
depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE)
|
2009-12-15 10:00:25 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
2006-09-29 16:59:00 +08:00
|
|
|
config DEBUG_LIST
|
|
|
|
bool "Debug linked list manipulation"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Enable this to turn on extended checks in the linked-list
|
|
|
|
walking routines.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2014-06-05 07:11:54 +08:00
|
|
|
config DEBUG_PI_LIST
|
|
|
|
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.
|
|
|
|
|
2007-10-23 02:01:06 +08:00
|
|
|
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.
|
|
|
|
|
2008-08-16 06:29:38 +08:00
|
|
|
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.
|
|
|
|
|
2009-09-02 16:13:40 +08:00
|
|
|
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.
|
|
|
|
|
2013-01-08 00:19:23 +08:00
|
|
|
menu "RCU Debugging"
|
|
|
|
|
|
|
|
config PROVE_RCU
|
2015-01-19 10:01:21 +08:00
|
|
|
def_bool PROVE_LOCKING
|
2013-01-08 00:19:23 +08:00
|
|
|
|
|
|
|
config PROVE_RCU_REPEATEDLY
|
|
|
|
bool "RCU debugging: don't disable PROVE_RCU on first splat"
|
|
|
|
depends on PROVE_RCU
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
By itself, PROVE_RCU will disable checking upon issuing the
|
|
|
|
first warning (or "splat"). This feature prevents such
|
|
|
|
disabling, allowing multiple RCU-lockdep warnings to be printed
|
|
|
|
on a single reboot.
|
|
|
|
|
|
|
|
Say Y to allow multiple RCU-lockdep warnings per boot.
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
config SPARSE_RCU_POINTER
|
|
|
|
bool "RCU debugging: sparse-based checks for pointer usage"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This feature enables the __rcu sparse annotation for
|
|
|
|
RCU-protected pointers. This annotation will cause sparse
|
|
|
|
to flag any non-RCU used of annotated pointers. This can be
|
|
|
|
helpful when debugging RCU usage. Please note that this feature
|
|
|
|
is not intended to enforce code cleanliness; it is instead merely
|
|
|
|
a debugging aid.
|
|
|
|
|
|
|
|
Say Y to make sparse flag questionable use of RCU-protected pointers
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
2014-01-28 03:49:39 +08:00
|
|
|
config TORTURE_TEST
|
|
|
|
tristate
|
|
|
|
default n
|
|
|
|
|
2016-01-01 10:33:22 +08:00
|
|
|
config RCU_PERF_TEST
|
|
|
|
tristate "performance tests for RCU"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
select TORTURE_TEST
|
|
|
|
select SRCU
|
|
|
|
select TASKS_RCU
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option provides a kernel module that runs performance
|
|
|
|
tests on the RCU infrastructure. The kernel module may be built
|
|
|
|
after the fact on the running kernel to be tested, if desired.
|
|
|
|
|
|
|
|
Say Y here if you want RCU performance tests to be built into
|
|
|
|
the kernel.
|
|
|
|
Say M if you want the RCU performance tests to build as a module.
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
2005-10-31 07:03:12 +08:00
|
|
|
config RCU_TORTURE_TEST
|
|
|
|
tristate "torture tests for RCU"
|
|
|
|
depends on DEBUG_KERNEL
|
2014-01-28 03:49:39 +08:00
|
|
|
select TORTURE_TEST
|
2014-12-06 00:24:45 +08:00
|
|
|
select SRCU
|
2015-04-20 20:42:50 +08:00
|
|
|
select TASKS_RCU
|
2005-10-31 07:03:12 +08:00
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option provides a kernel module that runs torture tests
|
|
|
|
on the RCU infrastructure. The kernel module may be built
|
|
|
|
after the fact on the running kernel to be tested, if desired.
|
|
|
|
|
2008-06-19 00:26:49 +08:00
|
|
|
Say Y here if you want RCU torture tests to be built into
|
|
|
|
the kernel.
|
2005-10-31 07:03:12 +08:00
|
|
|
Say M if you want the RCU torture tests to build as a module.
|
|
|
|
Say N if you are unsure.
|
2006-10-02 17:17:36 +08:00
|
|
|
|
2015-03-11 09:33:20 +08:00
|
|
|
config RCU_TORTURE_TEST_SLOW_PREINIT
|
|
|
|
bool "Slow down RCU grace-period pre-initialization to expose races"
|
|
|
|
depends on RCU_TORTURE_TEST
|
|
|
|
help
|
|
|
|
This option delays grace-period pre-initialization (the
|
|
|
|
propagation of CPU-hotplug changes up the rcu_node combining
|
|
|
|
tree) for a few jiffies between initializing each pair of
|
|
|
|
consecutive rcu_node structures. This helps to expose races
|
|
|
|
involving grace-period pre-initialization, in other words, it
|
|
|
|
makes your kernel less stable. It can also greatly increase
|
|
|
|
grace-period latency, especially on systems with large numbers
|
|
|
|
of CPUs. This is useful when torture-testing RCU, but in
|
|
|
|
almost no other circumstance.
|
|
|
|
|
|
|
|
Say Y here if you want your system to crash and hang more often.
|
|
|
|
Say N if you want a sane system.
|
|
|
|
|
|
|
|
config RCU_TORTURE_TEST_SLOW_PREINIT_DELAY
|
|
|
|
int "How much to slow down RCU grace-period pre-initialization"
|
|
|
|
range 0 5
|
|
|
|
default 3
|
|
|
|
depends on RCU_TORTURE_TEST_SLOW_PREINIT
|
|
|
|
help
|
|
|
|
This option specifies the number of jiffies to wait between
|
|
|
|
each rcu_node structure pre-initialization step.
|
|
|
|
|
2015-01-23 10:24:08 +08:00
|
|
|
config RCU_TORTURE_TEST_SLOW_INIT
|
|
|
|
bool "Slow down RCU grace-period initialization to expose races"
|
|
|
|
depends on RCU_TORTURE_TEST
|
|
|
|
help
|
2015-03-11 09:33:20 +08:00
|
|
|
This option delays grace-period initialization for a few
|
|
|
|
jiffies between initializing each pair of consecutive
|
2015-01-23 10:24:08 +08:00
|
|
|
rcu_node structures. This helps to expose races involving
|
|
|
|
grace-period initialization, in other words, it makes your
|
|
|
|
kernel less stable. It can also greatly increase grace-period
|
|
|
|
latency, especially on systems with large numbers of CPUs.
|
|
|
|
This is useful when torture-testing RCU, but in almost no
|
|
|
|
other circumstance.
|
|
|
|
|
|
|
|
Say Y here if you want your system to crash and hang more often.
|
|
|
|
Say N if you want a sane system.
|
|
|
|
|
|
|
|
config RCU_TORTURE_TEST_SLOW_INIT_DELAY
|
|
|
|
int "How much to slow down RCU grace-period initialization"
|
|
|
|
range 0 5
|
2015-01-30 08:37:19 +08:00
|
|
|
default 3
|
2015-04-15 10:33:59 +08:00
|
|
|
depends on RCU_TORTURE_TEST_SLOW_INIT
|
2015-01-23 10:24:08 +08:00
|
|
|
help
|
|
|
|
This option specifies the number of jiffies to wait between
|
|
|
|
each rcu_node structure initialization.
|
|
|
|
|
2015-03-11 09:33:20 +08:00
|
|
|
config RCU_TORTURE_TEST_SLOW_CLEANUP
|
|
|
|
bool "Slow down RCU grace-period cleanup to expose races"
|
|
|
|
depends on RCU_TORTURE_TEST
|
|
|
|
help
|
|
|
|
This option delays grace-period cleanup for a few jiffies
|
|
|
|
between cleaning up each pair of consecutive rcu_node
|
|
|
|
structures. This helps to expose races involving grace-period
|
|
|
|
cleanup, in other words, it makes your kernel less stable.
|
|
|
|
It can also greatly increase grace-period latency, especially
|
|
|
|
on systems with large numbers of CPUs. This is useful when
|
|
|
|
torture-testing RCU, but in almost no other circumstance.
|
|
|
|
|
|
|
|
Say Y here if you want your system to crash and hang more often.
|
|
|
|
Say N if you want a sane system.
|
|
|
|
|
|
|
|
config RCU_TORTURE_TEST_SLOW_CLEANUP_DELAY
|
|
|
|
int "How much to slow down RCU grace-period cleanup"
|
|
|
|
range 0 5
|
|
|
|
default 3
|
|
|
|
depends on RCU_TORTURE_TEST_SLOW_CLEANUP
|
|
|
|
help
|
|
|
|
This option specifies the number of jiffies to wait between
|
|
|
|
each rcu_node structure cleanup operation.
|
|
|
|
|
2010-06-03 07:21:38 +08:00
|
|
|
config RCU_CPU_STALL_TIMEOUT
|
|
|
|
int "RCU CPU stall timeout in seconds"
|
2012-10-20 03:49:17 +08:00
|
|
|
depends on RCU_STALL_COMMON
|
2010-06-03 07:21:38 +08:00
|
|
|
range 3 300
|
2012-10-26 08:59:23 +08:00
|
|
|
default 21
|
2010-06-03 07:21:38 +08:00
|
|
|
help
|
|
|
|
If a given RCU grace period extends more than the specified
|
|
|
|
number of seconds, a CPU stall warning is printed. If the
|
|
|
|
RCU grace period persists, additional CPU stall warnings are
|
|
|
|
printed at more widely spaced intervals.
|
|
|
|
|
2012-01-07 07:10:44 +08:00
|
|
|
config RCU_TRACE
|
|
|
|
bool "Enable tracing for RCU"
|
2008-01-30 20:33:08 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2012-11-15 08:26:40 +08:00
|
|
|
select TRACE_CLOCK
|
2008-01-30 20:33:08 +08:00
|
|
|
help
|
2012-01-07 07:10:44 +08:00
|
|
|
This option provides tracing in RCU which presents stats
|
|
|
|
in debugfs for debugging RCU implementation.
|
2008-06-28 00:04:48 +08:00
|
|
|
|
2012-01-07 07:10:44 +08:00
|
|
|
Say Y here if you want to enable RCU tracing
|
2008-01-30 20:33:08 +08:00
|
|
|
Say N if you are unsure.
|
|
|
|
|
2015-05-06 14:04:22 +08:00
|
|
|
config RCU_EQS_DEBUG
|
2015-07-01 00:56:31 +08:00
|
|
|
bool "Provide debugging asserts for adding NO_HZ support to an arch"
|
2015-05-06 14:04:22 +08:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
This option provides consistency checks in RCU's handling of
|
|
|
|
NO_HZ. These checks have proven quite helpful in detecting
|
|
|
|
bugs in arch-specific NO_HZ code.
|
|
|
|
|
|
|
|
Say N here if you need ultimate kernel/user switch latencies
|
|
|
|
Say Y if you are unsure
|
|
|
|
|
2013-01-08 00:19:23 +08:00
|
|
|
endmenu # "RCU Debugging"
|
|
|
|
|
2016-02-10 06:59:38 +08:00
|
|
|
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.
|
|
|
|
|
2008-08-25 18:47:25 +08:00
|
|
|
config DEBUG_BLOCK_EXT_DEVT
|
|
|
|
bool "Force extended block device numbers and spread them"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
depends on BLOCK
|
2008-08-29 15:06:29 +08:00
|
|
|
default n
|
2008-08-25 18:47:25 +08:00
|
|
|
help
|
2008-10-13 16:46:01 +08:00
|
|
|
BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
|
|
|
|
SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
|
|
|
|
YOU ARE DOING. Distros, please enable this and fix whatever
|
|
|
|
is broken.
|
|
|
|
|
2008-08-25 18:47:25 +08:00
|
|
|
Conventionally, block device numbers are allocated from
|
|
|
|
predetermined contiguous area. However, extended block area
|
|
|
|
may introduce non-contiguous block device numbers. This
|
|
|
|
option forces most block device numbers to be allocated from
|
|
|
|
the extended space and spreads them to discover kernel or
|
|
|
|
userland code paths which assume predetermined contiguous
|
|
|
|
device number allocation.
|
|
|
|
|
2008-09-01 19:44:35 +08:00
|
|
|
Note that turning on this debug option shuffles all the
|
|
|
|
device numbers for all IDE and SCSI devices including libata
|
|
|
|
ones, so root partition specified using device number
|
|
|
|
directly (via rdev or root=MAJ:MIN) won't work anymore.
|
|
|
|
Textual device names (root=/dev/sdXn) will continue to work.
|
|
|
|
|
2008-08-25 18:47:25 +08:00
|
|
|
Say N if you are unsure.
|
|
|
|
|
2016-02-27 02:43:32 +08:00
|
|
|
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.
|
|
|
|
|
2012-07-31 05:43:02 +08:00
|
|
|
config NOTIFIER_ERROR_INJECTION
|
|
|
|
tristate "Notifier error injection"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
select DEBUG_FS
|
|
|
|
help
|
2012-11-30 15:44:39 +08:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-07-31 05:43:02 +08:00
|
|
|
specified notifier chain callbacks. It is useful to test the error
|
|
|
|
handling of notifier call chain failures.
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
2010-05-27 05:43:36 +08:00
|
|
|
config CPU_NOTIFIER_ERROR_INJECT
|
|
|
|
tristate "CPU notifier error injection module"
|
2012-07-31 05:43:03 +08:00
|
|
|
depends on HOTPLUG_CPU && NOTIFIER_ERROR_INJECTION
|
2010-05-27 05:43:36 +08:00
|
|
|
help
|
|
|
|
This option provides a kernel module that can be used to test
|
2012-11-30 15:44:39 +08:00
|
|
|
the error handling of the cpu notifiers by injecting artificial
|
2012-07-31 05:43:03 +08:00
|
|
|
errors to CPU notifier chain callbacks. It is controlled through
|
|
|
|
debugfs interface under /sys/kernel/debug/notifier-error-inject/cpu
|
|
|
|
|
|
|
|
If the notifier call chain should be failed with some events
|
|
|
|
notified, write the error code to "actions/<notifier event>/error".
|
|
|
|
|
|
|
|
Example: Inject CPU offline error (-1 == -EPERM)
|
|
|
|
|
|
|
|
# cd /sys/kernel/debug/notifier-error-inject/cpu
|
|
|
|
# echo -1 > actions/CPU_DOWN_PREPARE/error
|
|
|
|
# echo 0 > /sys/devices/system/cpu/cpu1/online
|
|
|
|
bash: echo: write error: Operation not permitted
|
2010-05-27 05:43:36 +08:00
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
be called cpu-notifier-error-inject.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2012-07-31 05:43:07 +08:00
|
|
|
config PM_NOTIFIER_ERROR_INJECT
|
|
|
|
tristate "PM notifier error injection module"
|
|
|
|
depends on PM && NOTIFIER_ERROR_INJECTION
|
|
|
|
default m if PM_DEBUG
|
|
|
|
help
|
2012-11-30 15:44:39 +08:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-07-31 05:43:07 +08:00
|
|
|
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.
|
|
|
|
|
2012-12-14 07:32:52 +08:00
|
|
|
config OF_RECONFIG_NOTIFIER_ERROR_INJECT
|
|
|
|
tristate "OF reconfig notifier error injection module"
|
|
|
|
depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION
|
2012-07-31 05:43:13 +08:00
|
|
|
help
|
2012-11-30 15:44:39 +08:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-12-14 07:32:52 +08:00
|
|
|
OF reconfig notifier chain callbacks. It is controlled
|
2012-07-31 05:43:13 +08:00
|
|
|
through debugfs interface under
|
2012-12-14 07:32:52 +08:00
|
|
|
/sys/kernel/debug/notifier-error-inject/OF-reconfig/
|
2012-07-31 05:43:13 +08:00
|
|
|
|
|
|
|
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
|
2013-05-01 06:28:49 +08:00
|
|
|
be called of-reconfig-notifier-error-inject.
|
2012-07-31 05:43:13 +08:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2015-11-28 20:45:28 +08:00
|
|
|
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.
|
|
|
|
|
2006-12-08 18:39:43 +08:00
|
|
|
config FAULT_INJECTION
|
2006-12-08 18:39:49 +08:00
|
|
|
bool "Fault-injection framework"
|
|
|
|
depends on DEBUG_KERNEL
|
2006-12-08 18:39:48 +08:00
|
|
|
help
|
|
|
|
Provide fault-injection framework.
|
|
|
|
For more details, see Documentation/fault-injection/.
|
2006-12-08 18:39:43 +08:00
|
|
|
|
2006-12-08 18:39:44 +08:00
|
|
|
config FAILSLAB
|
2006-12-08 18:39:49 +08:00
|
|
|
bool "Fault-injection capability for kmalloc"
|
|
|
|
depends on FAULT_INJECTION
|
2008-12-23 18:37:01 +08:00
|
|
|
depends on SLAB || SLUB
|
2006-12-08 18:39:44 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for kmalloc.
|
2006-12-08 18:39:44 +08:00
|
|
|
|
2006-12-08 18:39:45 +08:00
|
|
|
config FAIL_PAGE_ALLOC
|
|
|
|
bool "Fault-injection capabilitiy for alloc_pages()"
|
2006-12-08 18:39:49 +08:00
|
|
|
depends on FAULT_INJECTION
|
2006-12-08 18:39:45 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for alloc_pages().
|
2006-12-08 18:39:45 +08:00
|
|
|
|
2006-12-08 18:39:46 +08:00
|
|
|
config FAIL_MAKE_REQUEST
|
2006-12-13 03:16:36 +08:00
|
|
|
bool "Fault-injection capability for disk IO"
|
2008-09-14 20:56:33 +08:00
|
|
|
depends on FAULT_INJECTION && BLOCK
|
2006-12-08 18:39:46 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for disk IO.
|
2006-12-08 18:39:46 +08:00
|
|
|
|
2008-09-14 20:56:33 +08:00
|
|
|
config FAIL_IO_TIMEOUT
|
2010-07-21 15:05:53 +08:00
|
|
|
bool "Fault-injection capability for faking disk interrupts"
|
2008-09-14 20:56:33 +08:00
|
|
|
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,
|
|
|
|
for others it wont do anything.
|
|
|
|
|
2011-08-19 20:52:37 +08:00
|
|
|
config FAIL_MMC_REQUEST
|
|
|
|
bool "Fault-injection capability for MMC IO"
|
2015-11-11 03:12:19 +08:00
|
|
|
depends on FAULT_INJECTION_DEBUG_FS && MMC
|
2011-08-19 20:52:37 +08:00
|
|
|
help
|
|
|
|
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.
|
|
|
|
|
2015-06-30 14:26:02 +08:00
|
|
|
config FAIL_FUTEX
|
|
|
|
bool "Fault-injection capability for futexes"
|
|
|
|
select DEBUG_FS
|
|
|
|
depends on FAULT_INJECTION && FUTEX
|
|
|
|
help
|
|
|
|
Provide fault-injection capability for futexes.
|
|
|
|
|
2006-12-08 18:39:43 +08:00
|
|
|
config FAULT_INJECTION_DEBUG_FS
|
|
|
|
bool "Debugfs entries for fault-injection capabilities"
|
2006-12-08 18:39:49 +08:00
|
|
|
depends on FAULT_INJECTION && SYSFS && DEBUG_FS
|
2006-12-08 18:39:43 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Enable configuration of fault-injection capabilities via debugfs.
|
2007-02-21 05:57:56 +08:00
|
|
|
|
|
|
|
config FAULT_INJECTION_STACKTRACE_FILTER
|
|
|
|
bool "stacktrace filter for fault-injection capabilities"
|
|
|
|
depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
|
2007-05-13 01:36:53 +08:00
|
|
|
depends on !X86_64
|
2007-02-21 05:57:56 +08:00
|
|
|
select STACKTRACE
|
2014-06-24 04:22:04 +08:00
|
|
|
select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND && !ARC && !SCORE
|
2007-02-21 05:57:56 +08:00
|
|
|
help
|
|
|
|
Provide stacktrace filter for fault-injection capabilities
|
2007-10-19 14:41:07 +08:00
|
|
|
|
2008-01-26 04:08:34 +08:00
|
|
|
config LATENCYTOP
|
|
|
|
bool "Latency measuring infrastructure"
|
2010-08-13 03:31:21 +08:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
depends on PROC_FS
|
2013-08-27 16:22:51 +08:00
|
|
|
select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND && !ARC
|
2008-01-26 04:08:34 +08:00
|
|
|
select KALLSYMS
|
|
|
|
select KALLSYMS_ALL
|
|
|
|
select STACKTRACE
|
|
|
|
select SCHEDSTATS
|
|
|
|
select SCHED_DEBUG
|
|
|
|
help
|
|
|
|
Enable this option if you want to use the LatencyTOP tool
|
|
|
|
to find out which userspace is blocking on what kernel operations.
|
|
|
|
|
2008-05-13 03:20:42 +08:00
|
|
|
source kernel/trace/Kconfig
|
|
|
|
|
2013-07-02 04:04:44 +08:00
|
|
|
menu "Runtime Testing"
|
|
|
|
|
|
|
|
config LKDTM
|
|
|
|
tristate "Linux Kernel Dump Test Tool Module"
|
|
|
|
depends on DEBUG_FS
|
|
|
|
depends on BLOCK
|
|
|
|
default n
|
|
|
|
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
|
|
|
|
Documentation/fault-injection/provoke-crashes.txt
|
|
|
|
|
|
|
|
config TEST_LIST_SORT
|
|
|
|
bool "Linked list sorting test"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Enable this to turn on 'list_sort()' function test. This test is
|
|
|
|
executed only once during system boot, so affects only boot time.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config KPROBES_SANITY_TEST
|
|
|
|
bool "Kprobes sanity tests"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
depends on KPROBES
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option provides for testing basic kprobes functionality on
|
|
|
|
boot. A sample kprobe, jprobe and kretprobe are inserted and
|
|
|
|
verified for functionality.
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
config BACKTRACE_SELF_TEST
|
|
|
|
tristate "Self test for the backtrace code"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
default n
|
|
|
|
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.
|
|
|
|
|
2012-10-09 07:30:39 +08:00
|
|
|
config RBTREE_TEST
|
|
|
|
tristate "Red-Black tree test"
|
2013-09-12 05:25:19 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2012-10-09 07:30:39 +08:00
|
|
|
help
|
|
|
|
A benchmark measuring the performance of the rbtree library.
|
|
|
|
Also includes rbtree invariant checks.
|
|
|
|
|
rbtree: add prio tree and interval tree tests
Patch 1 implements support for interval trees, on top of the augmented
rbtree API. It also adds synthetic tests to compare the performance of
interval trees vs prio trees. Short answers is that interval trees are
slightly faster (~25%) on insert/erase, and much faster (~2.4 - 3x)
on search. It is debatable how realistic the synthetic test is, and I have
not made such measurements yet, but my impression is that interval trees
would still come out faster.
Patch 2 uses a preprocessor template to make the interval tree generic,
and uses it as a replacement for the vma prio_tree.
Patch 3 takes the other prio_tree user, kmemleak, and converts it to use
a basic rbtree. We don't actually need the augmented rbtree support here
because the intervals are always non-overlapping.
Patch 4 removes the now-unused prio tree library.
Patch 5 proposes an additional optimization to rb_erase_augmented, now
providing it as an inline function so that the augmented callbacks can be
inlined in. This provides an additional 5-10% performance improvement
for the interval tree insert/erase benchmark. There is a maintainance cost
as it exposes augmented rbtree users to some of the rbtree library internals;
however I think this cost shouldn't be too high as I expect the augmented
rbtree will always have much less users than the base rbtree.
I should probably add a quick summary of why I think it makes sense to
replace prio trees with augmented rbtree based interval trees now. One of
the drivers is that we need augmented rbtrees for Rik's vma gap finding
code, and once you have them, it just makes sense to use them for interval
trees as well, as this is the simpler and more well known algorithm. prio
trees, in comparison, seem *too* clever: they impose an additional 'heap'
constraint on the tree, which they use to guarantee a faster worst-case
complexity of O(k+log N) for stabbing queries in a well-balanced prio
tree, vs O(k*log N) for interval trees (where k=number of matches,
N=number of intervals). Now this sounds great, but in practice prio trees
don't realize this theorical benefit. First, the additional constraint
makes them harder to update, so that the kernel implementation has to
simplify things by balancing them like a radix tree, which is not always
ideal. Second, the fact that there are both index and heap properties
makes both tree manipulation and search more complex, which results in a
higher multiplicative time constant. As it turns out, the simple interval
tree algorithm ends up running faster than the more clever prio tree.
This patch:
Add two test modules:
- prio_tree_test measures the performance of lib/prio_tree.c, both for
insertion/removal and for stabbing searches
- interval_tree_test measures the performance of a library of equivalent
functionality, built using the augmented rbtree support.
In order to support the second test module, lib/interval_tree.c is
introduced. It is kept separate from the interval_tree_test main file
for two reasons: first we don't want to provide an unfair advantage
over prio_tree_test by having everything in a single compilation unit,
and second there is the possibility that the interval tree functionality
could get some non-test users in kernel over time.
Signed-off-by: Michel Lespinasse <walken@google.com>
Cc: Rik van Riel <riel@redhat.com>
Cc: Hillf Danton <dhillf@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-10-09 07:31:23 +08:00
|
|
|
config INTERVAL_TREE_TEST
|
|
|
|
tristate "Interval tree test"
|
|
|
|
depends on m && DEBUG_KERNEL
|
2014-03-17 20:21:54 +08:00
|
|
|
select INTERVAL_TREE
|
rbtree: add prio tree and interval tree tests
Patch 1 implements support for interval trees, on top of the augmented
rbtree API. It also adds synthetic tests to compare the performance of
interval trees vs prio trees. Short answers is that interval trees are
slightly faster (~25%) on insert/erase, and much faster (~2.4 - 3x)
on search. It is debatable how realistic the synthetic test is, and I have
not made such measurements yet, but my impression is that interval trees
would still come out faster.
Patch 2 uses a preprocessor template to make the interval tree generic,
and uses it as a replacement for the vma prio_tree.
Patch 3 takes the other prio_tree user, kmemleak, and converts it to use
a basic rbtree. We don't actually need the augmented rbtree support here
because the intervals are always non-overlapping.
Patch 4 removes the now-unused prio tree library.
Patch 5 proposes an additional optimization to rb_erase_augmented, now
providing it as an inline function so that the augmented callbacks can be
inlined in. This provides an additional 5-10% performance improvement
for the interval tree insert/erase benchmark. There is a maintainance cost
as it exposes augmented rbtree users to some of the rbtree library internals;
however I think this cost shouldn't be too high as I expect the augmented
rbtree will always have much less users than the base rbtree.
I should probably add a quick summary of why I think it makes sense to
replace prio trees with augmented rbtree based interval trees now. One of
the drivers is that we need augmented rbtrees for Rik's vma gap finding
code, and once you have them, it just makes sense to use them for interval
trees as well, as this is the simpler and more well known algorithm. prio
trees, in comparison, seem *too* clever: they impose an additional 'heap'
constraint on the tree, which they use to guarantee a faster worst-case
complexity of O(k+log N) for stabbing queries in a well-balanced prio
tree, vs O(k*log N) for interval trees (where k=number of matches,
N=number of intervals). Now this sounds great, but in practice prio trees
don't realize this theorical benefit. First, the additional constraint
makes them harder to update, so that the kernel implementation has to
simplify things by balancing them like a radix tree, which is not always
ideal. Second, the fact that there are both index and heap properties
makes both tree manipulation and search more complex, which results in a
higher multiplicative time constant. As it turns out, the simple interval
tree algorithm ends up running faster than the more clever prio tree.
This patch:
Add two test modules:
- prio_tree_test measures the performance of lib/prio_tree.c, both for
insertion/removal and for stabbing searches
- interval_tree_test measures the performance of a library of equivalent
functionality, built using the augmented rbtree support.
In order to support the second test module, lib/interval_tree.c is
introduced. It is kept separate from the interval_tree_test main file
for two reasons: first we don't want to provide an unfair advantage
over prio_tree_test by having everything in a single compilation unit,
and second there is the possibility that the interval tree functionality
could get some non-test users in kernel over time.
Signed-off-by: Michel Lespinasse <walken@google.com>
Cc: Rik van Riel <riel@redhat.com>
Cc: Hillf Danton <dhillf@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-10-09 07:31:23 +08:00
|
|
|
help
|
|
|
|
A benchmark measuring the performance of the interval tree library
|
|
|
|
|
2013-11-13 07:08:34 +08:00
|
|
|
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.
|
|
|
|
|
2013-07-02 04:04:44 +08:00
|
|
|
config ATOMIC64_SELFTEST
|
|
|
|
bool "Perform an atomic64_t self-test at boot"
|
|
|
|
help
|
|
|
|
Enable this option to test the atomic64_t functions at boot.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config ASYNC_RAID6_TEST
|
|
|
|
tristate "Self test for hardware accelerated raid6 recovery"
|
|
|
|
depends on ASYNC_RAID6_RECOV
|
|
|
|
select ASYNC_MEMCPY
|
|
|
|
---help---
|
|
|
|
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.
|
|
|
|
|
2015-02-13 07:02:21 +08:00
|
|
|
config TEST_HEXDUMP
|
|
|
|
tristate "Test functions located in the hexdump module at runtime"
|
|
|
|
|
2013-07-02 04:04:44 +08:00
|
|
|
config TEST_STRING_HELPERS
|
|
|
|
tristate "Test functions located in the string_helpers module at runtime"
|
|
|
|
|
|
|
|
config TEST_KSTRTOX
|
|
|
|
tristate "Test kstrto*() family of functions at runtime"
|
|
|
|
|
2015-11-07 08:30:29 +08:00
|
|
|
config TEST_PRINTF
|
|
|
|
tristate "Test printf() family of functions at runtime"
|
|
|
|
|
2016-02-19 22:24:00 +08:00
|
|
|
config TEST_BITMAP
|
|
|
|
tristate "Test bitmap_*() family of functions at runtime"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enable this option to test the bitmap functions at boot.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2016-05-30 22:40:41 +08:00
|
|
|
config TEST_UUID
|
|
|
|
tristate "Test functions located in the uuid module at runtime"
|
|
|
|
|
2014-08-02 17:47:44 +08:00
|
|
|
config TEST_RHASHTABLE
|
2015-01-29 22:40:25 +08:00
|
|
|
tristate "Perform selftest on resizable hash table"
|
2014-08-02 17:47:44 +08:00
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enable this option to test the rhashtable functions at boot.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2016-05-27 10:11:51 +08:00
|
|
|
config TEST_HASH
|
|
|
|
tristate "Perform selftest on hash functions"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Enable this option to test the kernel's integer (<linux/hash,h>)
|
|
|
|
and string (<linux/stringhash.h>) hash functions on boot
|
|
|
|
(or module load).
|
|
|
|
|
|
|
|
This is intended to help people writing architecture-specific
|
|
|
|
optimized versions. If unsure, say N.
|
|
|
|
|
2013-07-02 04:04:44 +08:00
|
|
|
endmenu # runtime tests
|
|
|
|
|
x86: early boot debugging via FireWire (ohci1394_dma=early)
This patch adds a new configuration option, which adds support for a new
early_param which gets checked in arch/x86/kernel/setup_{32,64}.c:setup_arch()
to decide wether OHCI-1394 FireWire controllers should be initialized and
enabled for physical DMA access to allow remote debugging of early problems
like issues ACPI or other subsystems which are executed very early.
If the config option is not enabled, no code is changed, and if the boot
paramenter is not given, no new code is executed, and independent of that,
all new code is freed after boot, so the config option can be even enabled
in standard, non-debug kernels.
With specialized tools, it is then possible to get debugging information
from machines which have no serial ports (notebooks) such as the printk
buffer contents, or any data which can be referenced from global pointers,
if it is stored below the 4GB limit and even memory dumps of of the physical
RAM region below the 4GB limit can be taken without any cooperation from the
CPU of the host, so the machine can be crashed early, it does not matter.
In the extreme, even kernel debuggers can be accessed in this way. I wrote
a small kgdb module and an accompanying gdb stub for FireWire which allows
to gdb to talk to kgdb using remote remory reads and writes over FireWire.
An version of the gdb stub fore FireWire is able to read all global data
from a system which is running a a normal kernel without any kernel debugger,
without any interruption or support of the system's CPU. That way, e.g. the
task struct and so on can be read and even manipulated when the physical DMA
access is granted.
A HOWTO is included in this patch, in Documentation/debugging-via-ohci1394.txt
and I've put a copy online at
ftp://ftp.suse.de/private/bk/firewire/docs/debugging-via-ohci1394.txt
It also has links to all the tools which are available to make use of it
another copy of it is online at:
ftp://ftp.suse.de/private/bk/firewire/kernel/ohci1394_dma_early-v2.diff
Signed-Off-By: Bernhard Kaindl <bk@suse.de>
Tested-By: Thomas Renninger <trenn@suse.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 20:34:11 +08:00
|
|
|
config PROVIDE_OHCI1394_DMA_INIT
|
2008-02-29 03:54:43 +08:00
|
|
|
bool "Remote debugging over FireWire early on boot"
|
x86: early boot debugging via FireWire (ohci1394_dma=early)
This patch adds a new configuration option, which adds support for a new
early_param which gets checked in arch/x86/kernel/setup_{32,64}.c:setup_arch()
to decide wether OHCI-1394 FireWire controllers should be initialized and
enabled for physical DMA access to allow remote debugging of early problems
like issues ACPI or other subsystems which are executed very early.
If the config option is not enabled, no code is changed, and if the boot
paramenter is not given, no new code is executed, and independent of that,
all new code is freed after boot, so the config option can be even enabled
in standard, non-debug kernels.
With specialized tools, it is then possible to get debugging information
from machines which have no serial ports (notebooks) such as the printk
buffer contents, or any data which can be referenced from global pointers,
if it is stored below the 4GB limit and even memory dumps of of the physical
RAM region below the 4GB limit can be taken without any cooperation from the
CPU of the host, so the machine can be crashed early, it does not matter.
In the extreme, even kernel debuggers can be accessed in this way. I wrote
a small kgdb module and an accompanying gdb stub for FireWire which allows
to gdb to talk to kgdb using remote remory reads and writes over FireWire.
An version of the gdb stub fore FireWire is able to read all global data
from a system which is running a a normal kernel without any kernel debugger,
without any interruption or support of the system's CPU. That way, e.g. the
task struct and so on can be read and even manipulated when the physical DMA
access is granted.
A HOWTO is included in this patch, in Documentation/debugging-via-ohci1394.txt
and I've put a copy online at
ftp://ftp.suse.de/private/bk/firewire/docs/debugging-via-ohci1394.txt
It also has links to all the tools which are available to make use of it
another copy of it is online at:
ftp://ftp.suse.de/private/bk/firewire/kernel/ohci1394_dma_early-v2.diff
Signed-Off-By: Bernhard Kaindl <bk@suse.de>
Tested-By: Thomas Renninger <trenn@suse.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 20:34:11 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
See Documentation/debugging-via-ohci1394.txt for more information.
|
2008-01-26 04:08:34 +08:00
|
|
|
|
2009-01-09 19:14:24 +08:00
|
|
|
config DMA_API_DEBUG
|
|
|
|
bool "Enable debugging of DMA-API usage"
|
|
|
|
depends on HAVE_DMA_API_DEBUG
|
|
|
|
help
|
|
|
|
Enable this option to debug the use of the DMA API by device drivers.
|
|
|
|
With this option you will be able to detect common bugs in device
|
|
|
|
drivers like double-freeing of DMA mappings or freeing mappings that
|
|
|
|
were never allocated.
|
2014-01-22 07:48:12 +08:00
|
|
|
|
|
|
|
This also attempts to catch cases where a page owned by DMA is
|
|
|
|
accessed by the cpu in a way that could cause data corruption. For
|
|
|
|
example, this enables cow_user_page() to check that the source page is
|
|
|
|
not undergoing DMA.
|
|
|
|
|
|
|
|
This option causes a performance degradation. Use only if you want to
|
|
|
|
debug device drivers and dma interactions.
|
|
|
|
|
|
|
|
If unsure, say N.
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-13 04:46:19 +08:00
|
|
|
|
2014-10-14 06:51:38 +08:00
|
|
|
config TEST_LKM
|
test: add minimal module for verification testing
This is a pair of test modules I'd like to see in the tree. Instead of
putting these in lkdtm, where I've been adding various tests that trigger
crashes, these don't make sense there since they need to be either
distinctly separate, or their pass/fail state don't need to crash the
machine.
These live in lib/ for now, along with a few other in-kernel test modules,
and use the slightly more common "test_" naming convention, instead of
"test-". We should likely standardize on the former:
$ find . -name 'test_*.c' | grep -v /tools/ | wc -l
4
$ find . -name 'test-*.c' | grep -v /tools/ | wc -l
2
The first is entirely a no-op module, designed to allow simple testing of
the module loading and verification interface. It's useful to have a
module that has no other uses or dependencies so it can be reliably used
for just testing module loading and verification.
The second is a module that exercises the user memory access functions, in
an effort to make sure that we can quickly catch any regressions in
boundary checking (e.g. like what was recently fixed on ARM).
This patch (of 2):
When doing module loading verification tests (for example, with module
signing, or LSM hooks), it is very handy to have a module that can be
built on all systems under test, isn't auto-loaded at boot, and has no
device or similar dependencies. This creates the "test_module.ko" module
for that purpose, which only reports its load and unload to printk.
Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Joe Perches <joe@perches.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-01-24 07:54:37 +08:00
|
|
|
tristate "Test module loading with 'hello world' module"
|
|
|
|
default n
|
|
|
|
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.
|
|
|
|
|
2014-01-24 07:54:38 +08:00
|
|
|
config TEST_USER_COPY
|
|
|
|
tristate "Test user/kernel boundary protections"
|
|
|
|
default n
|
|
|
|
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.
|
|
|
|
|
2014-05-09 05:10:52 +08:00
|
|
|
config TEST_BPF
|
|
|
|
tristate "Test BPF filter functionality"
|
|
|
|
default n
|
2014-05-14 00:58:44 +08:00
|
|
|
depends on m && NET
|
2014-05-09 05:10:52 +08:00
|
|
|
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
|
bpf: mini eBPF library, test stubs and verifier testsuite
1.
the library includes a trivial set of BPF syscall wrappers:
int bpf_create_map(int key_size, int value_size, int max_entries);
int bpf_update_elem(int fd, void *key, void *value);
int bpf_lookup_elem(int fd, void *key, void *value);
int bpf_delete_elem(int fd, void *key);
int bpf_get_next_key(int fd, void *key, void *next_key);
int bpf_prog_load(enum bpf_prog_type prog_type,
const struct sock_filter_int *insns, int insn_len,
const char *license);
bpf_prog_load() stores verifier log into global bpf_log_buf[] array
and BPF_*() macros to build instructions
2.
test stubs configure eBPF infra with 'unspec' map and program types.
These are fake types used by user space testsuite only.
3.
verifier tests valid and invalid programs and expects predefined
error log messages from kernel.
40 tests so far.
$ sudo ./test_verifier
#0 add+sub+mul OK
#1 unreachable OK
#2 unreachable2 OK
#3 out of range jump OK
#4 out of range jump2 OK
#5 test1 ld_imm64 OK
...
Signed-off-by: Alexei Starovoitov <ast@plumgrid.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2014-09-26 15:17:07 +08:00
|
|
|
the interpreter code. It also enables test stubs for eBPF maps and
|
|
|
|
verifier used by user space verifier testsuite.
|
2014-05-09 05:10:52 +08:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2014-07-15 05:38:12 +08:00
|
|
|
config TEST_FIRMWARE
|
|
|
|
tristate "Test firmware loading via userspace interface"
|
|
|
|
default n
|
|
|
|
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.
|
|
|
|
|
2014-06-17 05:58:32 +08:00
|
|
|
config TEST_UDELAY
|
|
|
|
tristate "udelay test driver"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This builds the "udelay_test" module that helps to make sure
|
|
|
|
that udelay() is working properly.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2015-04-15 06:48:27 +08:00
|
|
|
config MEMTEST
|
|
|
|
bool "Memtest"
|
|
|
|
depends on HAVE_MEMBLOCK
|
|
|
|
---help---
|
|
|
|
This option adds a kernel parameter 'memtest', which allows memtest
|
|
|
|
to be set.
|
|
|
|
memtest=0, mean disabled; -- default
|
|
|
|
memtest=1, mean do 1 test pattern;
|
|
|
|
...
|
2015-04-15 06:48:40 +08:00
|
|
|
memtest=17, mean do 17 test patterns.
|
2015-04-15 06:48:27 +08:00
|
|
|
If you are unsure how to answer this question, answer N.
|
|
|
|
|
2015-08-03 17:42:57 +08:00
|
|
|
config TEST_STATIC_KEYS
|
|
|
|
tristate "Test static keys"
|
2015-07-30 11:59:44 +08:00
|
|
|
default n
|
|
|
|
depends on m
|
|
|
|
help
|
2015-08-03 17:42:57 +08:00
|
|
|
Test the static key interfaces.
|
2015-07-30 11:59:44 +08:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2007-10-19 14:41:07 +08:00
|
|
|
source "samples/Kconfig"
|
2008-04-18 02:05:37 +08:00
|
|
|
|
|
|
|
source "lib/Kconfig.kgdb"
|
2009-02-27 03:38:56 +08:00
|
|
|
|
2016-01-21 07:00:55 +08:00
|
|
|
source "lib/Kconfig.ubsan"
|
|
|
|
|
2015-11-20 10:19:29 +08:00
|
|
|
config ARCH_HAS_DEVMEM_IS_ALLOWED
|
|
|
|
bool
|
|
|
|
|
|
|
|
config STRICT_DEVMEM
|
|
|
|
bool "Filter access to /dev/mem"
|
|
|
|
depends on MMU
|
|
|
|
depends on ARCH_HAS_DEVMEM_IS_ALLOWED
|
|
|
|
default y if TILE || PPC
|
|
|
|
---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.
|
|
|
|
|
2015-11-24 07:49:03 +08:00
|
|
|
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.
|
|
|
|
|
2015-11-20 10:19:29 +08:00
|
|
|
If this option is switched on, the /dev/mem file only allows
|
2015-11-24 07:49:03 +08:00
|
|
|
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.
|
2015-11-20 10:19:29 +08:00
|
|
|
|
|
|
|
If in doubt, say Y.
|