From: Changbin Du <changbin.du@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Changbin Du <changbin.du@gmail.com>
Subject: [PATCH v2 6/9] kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE
Date: Mon, 9 Sep 2019 22:18:20 +0800 [thread overview]
Message-ID: <20190909141823.8638-7-changbin.du@gmail.com> (raw)
In-Reply-To: <20190909141823.8638-1-changbin.du@gmail.com>
They are both memory debug options to debug kernel stack issues.
Signed-off-by: Changbin Du <changbin.du@gmail.com>
---
lib/Kconfig.debug | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 1385e17122a1..ce545bb80ea2 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -652,6 +652,18 @@ config DEBUG_STACK_USAGE
This option will slow down process creation somewhat.
+config SCHED_STACK_END_CHECK
+ bool "Detect stack corruption on calls to schedule()"
+ depends on DEBUG_KERNEL
+ default n
+ help
+ This option checks for a stack overrun on calls to schedule().
+ If the stack end location is found to be over written always panic as
+ the content of the corrupted region can no longer be trusted.
+ This is to ensure no erroneous behaviour occurs which could result in
+ data corruption or a sporadic crash at a later stage once the region
+ is examined. The runtime overhead introduced is minimal.
+
config DEBUG_VM
bool "Debug VM"
depends on DEBUG_KERNEL
@@ -1005,18 +1017,6 @@ config SCHEDSTATS
application, you can say N to avoid the very slight overhead
this adds.
-config SCHED_STACK_END_CHECK
- bool "Detect stack corruption on calls to schedule()"
- depends on DEBUG_KERNEL
- default n
- help
- This option checks for a stack overrun on calls to schedule().
- If the stack end location is found to be over written always panic as
- the content of the corrupted region can no longer be trusted.
- This is to ensure no erroneous behaviour occurs which could result in
- data corruption or a sporadic crash at a later stage once the region
- is examined. The runtime overhead introduced is minimal.
-
config DEBUG_TIMEKEEPING
bool "Enable extra timekeeping sanity checking"
help
--
2.20.1
next prev parent reply other threads:[~2019-09-09 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 14:18 [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized Changbin Du
2019-09-09 14:18 ` [PATCH v2 1/9] kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-09 14:18 ` [PATCH v2 2/9] kconfig/hacking: Create submenu for arch special debugging options Changbin Du
2019-09-09 14:18 ` [PATCH v2 3/9] kconfig/hacking: Group kernel data structures debugging together Changbin Du
2019-09-09 14:18 ` [PATCH v2 4/9] kconfig/hacking: Move kernel testing and coverage options to same submenu Changbin Du
2019-09-09 14:18 ` [PATCH v2 5/9] kconfig/hacking: Move Oops into 'Lockups and Hangs' Changbin Du
2019-09-09 14:18 ` Changbin Du [this message]
2019-09-09 14:18 ` [PATCH v2 7/9] kconfig/hacking: Create a submenu for scheduler debugging options Changbin Du
2019-09-09 14:18 ` [PATCH v2 8/9] kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options' Changbin Du
2019-09-09 14:18 ` [PATCH v2 9/9] kconfig/hacking: Move DEBUG_FS to 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-09 14:31 ` [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized Masahiro Yamada
2019-09-09 14:41 ` 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=20190909141823.8638-7-changbin.du@gmail.com \
--to=changbin.du@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).