The patch titled
Subject: kernel-hacking: move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE
has been added to the -mm tree. Its filename is
hacking-move-sched_stack_end_check-after-debug_stack_usage.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/hacking-move-sched_stack_end_check-after-debug_stack_usage.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/hacking-move-sched_stack_end_check-after-debug_stack_usage.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Changbin Du <changbin.du@xxxxxxxxx>
Subject: kernel-hacking: move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE
They are both memory debug options to debug kernel stack issues.
Link: http://lkml.kernel.org/r/20190909144453.3520-7-changbin.du@xxxxxxxxx
Signed-off-by: Changbin Du <changbin.du@xxxxxxxxx>
Acked-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Tested-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
lib/Kconfig.debug | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
--- a/lib/Kconfig.debug~hacking-move-sched_stack_end_check-after-debug_stack_usage
+++ a/lib/Kconfig.debug
@@ -642,6 +642,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
@@ -995,18 +1007,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
_
Patches currently in -mm which might be from changbin.du@xxxxxxxxx are
hacking-group-sysrq-kgdb-ubsan-into-generic-kernel-debugging-instruments.patch
hacking-create-submenu-for-arch-special-debugging-options.patch
hacking-group-kernel-data-structures-debugging-together.patch
hacking-move-kernel-testing-and-coverage-options-to-same-submenu.patch
hacking-move-oops-into-lockups-and-hangs.patch
hacking-move-sched_stack_end_check-after-debug_stack_usage.patch
hacking-create-a-submenu-for-scheduler-debugging-options.patch
hacking-move-debug_bugverbose-to-printk-and-dmesg-options.patch
hacking-move-debug_fs-to-generic-kernel-debugging-instruments.patch
