public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Mullis <dwm@meer.net>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, akpm@osdl.org,
	Valdis.Kletnieks@vt.edu
Subject: Re: [patch 8/8] stacktrace filtering for fault-injection capabilities
Date: Mon, 18 Sep 2006 22:57:51 -0700	[thread overview]
Message-ID: <1158645471.2419.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20060914102033.462112306@localhost.localdomain>

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@meer.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.
-



  parent reply	other threads:[~2006-09-19  6:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 10:20 [patch 0/8] fault-injection capabilities (v3) Akinobu Mita
2006-09-14 10:20 ` [patch 1/8] documentation and scripts Akinobu Mita
2006-09-19  5:50   ` Don Mullis
2006-09-19  9:01     ` Akinobu Mita
2006-09-14 10:20 ` [patch 2/8] fault-injection capabilities infrastructure Akinobu Mita
2006-09-19  5:50   ` Don Mullis
2006-09-19  9:03     ` Akinobu Mita
2006-09-14 10:20 ` [patch 3/8] fault-injection capability for kmalloc Akinobu Mita
2006-09-14 10:20 ` [patch 4/8] fault-injection capability for alloc_pages() Akinobu Mita
2006-09-14 10:20 ` [patch 5/8] fault-injection capability for disk IO Akinobu Mita
2006-09-14 10:20 ` [patch 6/8] debugfs entries for configuration Akinobu Mita
2006-09-19  5:52   ` Don Mullis
2006-09-14 10:20 ` [patch 7/8] process filtering for fault-injection capabilities Akinobu Mita
2006-09-19  5:54   ` Don Mullis
2006-09-19  9:05     ` Akinobu Mita
2006-09-19 17:38       ` Don Mullis
2006-09-19  5:55   ` Don Mullis
2006-09-14 10:20 ` [patch 8/8] stacktrace " Akinobu Mita
2006-09-19  5:56   ` Don Mullis
2006-09-19  9:08     ` Akinobu Mita
2006-09-19  5:57   ` Don Mullis [this message]
2006-09-19  9:09     ` Akinobu Mita
2006-09-19 17:35       ` Don Mullis
2006-09-20 13:39         ` Akinobu Mita
2006-09-20 20:02           ` Don Mullis
     [not found] <20061010115219.176309702@gmail.com>
     [not found] ` <20061010115255.902380817@gmail.com>
2006-10-16  9:31   ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1158645471.2419.13.camel@localhost.localdomain \
    --to=dwm@meer.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mita@miraclelinux.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox