[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1158645471.2419.13.camel@localhost.localdomain>
Date: Mon, 18 Sep 2006 22:57:51 -0700
From: Don Mullis <dwm@...r.net>
To: Akinobu Mita <mita@...aclelinux.com>
Cc: linux-kernel@...r.kernel.org, ak@...e.de, akpm@...l.org,
Valdis.Kletnieks@...edu
Subject: Re: [patch 8/8] stacktrace filtering for fault-injection
capabilities
Push fault-injection entries earlier in the list, so that they appear
nested under DEBUG_KERNEL in menuconfig/xconfig.
Signed-off-by: Don Mullis <dwm@...r.net>
---
lib/Kconfig.debug | 70 +++++++++++++++++++++++++++---------------------------
1 file changed, 35 insertions(+), 35 deletions(-)
Index: linux-2.6.17/lib/Kconfig.debug
===================================================================
--- linux-2.6.17.orig/lib/Kconfig.debug
+++ linux-2.6.17/lib/Kconfig.debug
@@ -294,6 +294,41 @@ config DEBUG_INFO
If unsure, say N.
+config FAULT_INJECTION
+ bool
+ depends on DEBUG_KERNEL
+ select STACKTRACE
+ select FRAME_POINTER
+
+config FAILSLAB
+ bool "fault-injection capability for kmalloc"
+ depends on DEBUG_KERNEL
+ select FAULT_INJECTION
+ help
+ This option provides fault-injection capability for kmalloc.
+
+config FAIL_PAGE_ALLOC
+ bool "fault-injection capability for alloc_pages()"
+ depends on DEBUG_KERNEL
+ select FAULT_INJECTION
+ help
+ This option provides fault-injection capability for alloc_pages().
+
+config FAIL_MAKE_REQUEST
+ bool "fault-injection capability for disk IO"
+ depends on DEBUG_KERNEL
+ select FAULT_INJECTION
+ help
+ This option provides fault-injection capability to disk IO.
+
+config FAULT_INJECTION_DEBUGFS
+ tristate "runtime configuration for fault-injection capabilities"
+ depends on DEBUG_KERNEL && SYSFS && FAULT_INJECTION
+ select DEBUG_FS
+ help
+ This option provides kernel module that provides runtime
+ configuration interface by debugfs.
+
config DEBUG_FS
bool "Debug Filesystem"
depends on SYSFS
@@ -368,38 +403,3 @@ config RCU_TORTURE_TEST
at boot time (you probably don't).
Say M if you want the RCU torture tests to build as a module.
Say N if you are unsure.
-
-config FAULT_INJECTION
- bool
- select STACKTRACE
- select FRAME_POINTER
-
-config FAILSLAB
- bool "fault-injection capabilitiy for kmalloc"
- depends on DEBUG_KERNEL
- select FAULT_INJECTION
- help
- This option provides fault-injection capabilitiy for kmalloc.
-
-config FAIL_PAGE_ALLOC
- bool "fault-injection capabilitiy for alloc_pages()"
- depends on DEBUG_KERNEL
- select FAULT_INJECTION
- help
- This option provides fault-injection capabilitiy for alloc_pages().
-
-config FAIL_MAKE_REQUEST
- bool "fault-injection capabilitiy for disk IO"
- depends on DEBUG_KERNEL
- select FAULT_INJECTION
- help
- This option provides fault-injection capabilitiy to disk IO.
-
-config FAULT_INJECTION_DEBUGFS
- tristate "runtime configuration for fault-injection capabilities"
- depends on DEBUG_KERNEL && SYSFS && FAULT_INJECTION
- select DEBUG_FS
- help
- This option provides kernel module that provides runtime
- configuration interface by debugfs.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists