aboutsummaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2008-08-15 18:29:38 -0400
committerIngo Molnar <mingo@elte.hu>2008-09-10 03:08:50 -0400
commit1b2439dbb703ae8d95a9ce7ece6b7800b80f41f0 (patch)
tree63c6c105b86ce45ca010dca4bd501a924afd05d1 /lib
parentb09c3e3f1710b554348c98e78fbf4a661918779a (diff)
debug: add notifier chain debugging
during some development we suspected a case where we left something in a notifier chain that was from a module that was unloaded already... and that sort of thing is rather hard to track down. This patch adds a very simple sanity check (which isn't all that expensive) to make sure the notifier we're about to call is actually from either the kernel itself of from a still-loaded module, avoiding a hard-to-chase-down crash. Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'lib')
-rw-r--r--lib/Kconfig.debug10
1 files changed, 10 insertions, 0 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 8b5a7d304a5f..342858fbabbc 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -536,6 +536,16 @@ config DEBUG_SG
536 536
537 If unsure, say N. 537 If unsure, say N.
538 538
539config DEBUG_NOTIFIERS
540 bool "Debug notifier call chains"
541 depends on DEBUG_KERNEL
542 help
543 Enable this to turn on sanity checking for notifier call chains.
544 This is most useful for kernel developers to make sure that
545 modules properly unregister themselves from notifier chains.
546 This is a relatively cheap check but if you care about maximum
547 performance, say N.
548
539config FRAME_POINTER 549config FRAME_POINTER
540 bool "Compile the kernel with frame pointers" 550 bool "Compile the kernel with frame pointers"
541 depends on DEBUG_KERNEL && \ 551 depends on DEBUG_KERNEL && \