From: Changbin Du <changbin.du@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Changbin Du <changbin.du@gmail.com>
Subject: [PATCH 3/8] kconfig/hacking: Group kernel data structures debugging together
Date: Sun, 8 Sep 2019 09:27:55 +0800 [thread overview]
Message-ID: <20190908012800.12979-4-changbin.du@gmail.com> (raw)
In-Reply-To: <20190908012800.12979-1-changbin.du@gmail.com>
Group these similar runtime data structures verification options together.
Signed-off-by: Changbin Du <changbin.du@gmail.com>
---
lib/Kconfig.debug | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 96047140be93..3c9674483ec2 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1374,6 +1374,8 @@ config DEBUG_BUGVERBOSE
of the BUG call as well as the EIP and oops trace. This aids
debugging but costs about 70-100K of memory.
+menu "Debug kernel data structures"
+
config DEBUG_LIST
bool "Debug linked list manipulation"
depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION
@@ -1403,6 +1405,18 @@ config DEBUG_SG
If unsure, say N.
+config BUG_ON_DATA_CORRUPTION
+ bool "Trigger a BUG when data corruption is detected"
+ select DEBUG_LIST
+ help
+ Select this option if the kernel should BUG when it encounters
+ data corruption in kernel memory structures when they get checked
+ for validity.
+
+ If unsure, say N.
+
+endmenu
+
config DEBUG_NOTIFIERS
bool "Debug notifier call chains"
depends on DEBUG_KERNEL
@@ -2095,16 +2109,6 @@ config MEMTEST
memtest=17, mean do 17 test patterns.
If you are unsure how to answer this question, answer N.
-config BUG_ON_DATA_CORRUPTION
- bool "Trigger a BUG when data corruption is detected"
- select DEBUG_LIST
- help
- Select this option if the kernel should BUG when it encounters
- data corruption in kernel memory structures when they get checked
- for validity.
-
- If unsure, say N.
-
source "samples/Kconfig"
config ARCH_HAS_DEVMEM_IS_ALLOWED
--
2.20.1
next prev parent reply other threads:[~2019-09-08 1:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 1:27 [PATCH 0/8] kconfig/hacking: make 'kernel hacking' menu better structured Changbin Du
2019-09-08 1:27 ` [PATCH 1/8] kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-08 1:27 ` [PATCH 2/8] kconfig/hacking: Create submenu for arch special debugging options Changbin Du
2019-09-08 1:27 ` Changbin Du [this message]
2019-09-08 1:27 ` [PATCH 4/8] kconfig/hacking: Move kernel testing and coverage options to same submenu Changbin Du
2019-09-08 1:27 ` [PATCH 5/8] kconfig/hacking: Move Oops into 'Lockups and Hangs' Changbin Du
2019-09-08 1:27 ` [PATCH 6/8] kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE Changbin Du
2019-09-08 1:27 ` [PATCH 7/8] kconfig/hacking: Create a submenu for scheduler debugging options Changbin Du
2019-09-08 1:28 ` [PATCH 8/8] kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options' Changbin Du
2019-09-08 1:30 ` [PATCH 0/8] kconfig/hacking: make 'kernel hacking' menu better structured Changbin Du
2019-09-09 0:44 ` Randy Dunlap
2019-09-09 14:10 ` Changbin Du
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=20190908012800.12979-4-changbin.du@gmail.com \
--to=changbin.du@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome