path: root/lib/Kconfig.debug
diff options
authorMandeep Singh Baines <>2011-03-22 16:34:23 -0700
committerLinus Torvalds <>2011-03-22 17:44:13 -0700
commit5af5bcb8d37f99ba415a1adc6da71051b84f93a5 (patch)
tree58ae14d126ef40cbc5a91538cfe04433d26510ae /lib/Kconfig.debug
parent9f36e2c448007b54851e7e4fa48da97d1477a175 (diff)
printk: allow setting DEFAULT_MESSAGE_LEVEL via Kconfig
We've been burned by regressions/bugs which we later realized could have been triaged quicker if only we'd paid closer attention to dmesg. To make it easier to audit dmesg, we'd like to make DEFAULT_MESSAGE_LEVEL Kconfig-settable. That way we can set it to KERN_NOTICE and audit any messages <= KERN_WARNING. Signed-off-by: Mandeep Singh Baines <> Cc: Ingo Molnar <> Cc: Joe Perches <> Cc: Olof Johansson <> Cc: Randy Dunlap <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'lib/Kconfig.debug')
1 files changed, 11 insertions, 0 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index fb0afeff9436..bef5faab660f 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -9,6 +9,17 @@ config PRINTK_TIME
operations. This is useful for identifying long delays
in kernel startup.
+ 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.
bool "Enable __deprecated logic"
default y