Commit dc9b9638 authored by Changbin Du's avatar Changbin Du Committed by Linus Torvalds
Browse files

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@gmail.com


Signed-off-by: default avatarChangbin Du <changbin.du@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Tested-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent f43a289d

lib/Kconfig.debug

+12 −12
Original line number Diff line number Diff line
@@ -632,6 +632,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
@@ -985,18 +997,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

CRA Git | Maintained and supported by SUSTech CRA and CCSE