watchdog: Add sysctl knob hardlockup_panic
Subsystems (3)
PATCH v2 1/1 watchdog: Add sysctl knob hardlockup_panic
The only way to enable a hardlockup to panic the machine is to set 'nmi_watchdog=panic' on the kernel command line.
This makes it awkward for end users and folks who want to run automate tests (like myself).
Mimic the softlockup_panic knob and create a /proc/sys/kernel/hardlockup_panic knob.
--
V2 - wrap the sysctl variable with CONFIG_HARDLOCKUP_DETECTOR (kbuid bot)
--- Documentation/lockup-watchdogs.txt | 5 +++-- include/linux/sched.h | 1 + kernel/sysctl.c | 11 +++++++++++ kernel/watchdog.c | 2 +- 4 files changed, 16 insertions(+), 3 deletions(-)
Documentation/lockup-watchdogs.txt +3 -2
@@ -20,8 +20,9 @@ kernel mode for more than 10 seconds (see "Implementation" below for details), without letting other interrupts have a chance to run. Similarly to the softlockup case, the current stack trace is displayed upon detection and the system will stay locked up unless the default -behavior is changed, which can be done through a compile time knob, -"BOOTPARAM_HARDLOCKUP_PANIC", and a kernel parameter, "nmi_watchdog" +behavior is changed, which can be done through a sysctl, +'hardlockup_panic', a compile time knob, "BOOTPARAM_HARDLOCKUP_PANIC", +and a kernel parameter, "nmi_watchdog" (see "Documentation/kernel-parameters.txt" for details). The panic option can be used in combination with panic_timeout (this
include/linux/sched.h +1 -0
@@ -384,6 +384,7 @@ extern int proc_dowatchdog_thresh(struct ctl_table *table, int write,void __user *buffer, size_t *lenp, loff_t *ppos);extern unsigned int softlockup_panic; +extern unsigned int hardlockup_panic;void lockup_detector_init (void );#else static inline void touch_softlockup_watchdog (void )
kernel/sysctl.c +11 -0
@@ -887,6 +887,17 @@ static struct ctl_table kern_table[] = { .extra1 = &zero, .extra2 = &one, }, +#ifdef CONFIG_HARDLOCKUP_DETECTOR + { + .procname = "hardlockup_panic", + .data = &hardlockup_panic, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = &zero, + .extra2 = &one, + }, +#endif #ifdef CONFIG_SMP { .procname = "softlockup_all_cpu_backtrace",
kernel/watchdog.c +1 -1
@@ -112,7 +112,7 @@ static unsigned long soft_lockup_nmi_warn;* Should we panic when a soft-lockup or hard-lockup occurs: */ #ifdef CONFIG_HARDLOCKUP_DETECTOR -static int hardlockup_panic = +unsigned int __read_mostly hardlockup_panic =CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE ;static unsigned long hardlockup_allcpu_dumped;/*
Signature · 1 line
1.8.4
Quoted 75 lines · Don Zickus
The only way to enable a hardlockup to panic the machine is to set 'nmi_watchdog=panic' on the kernel command line.
This makes it awkward for end users and folks who want to run automate tests (like myself).
Mimic the
softlockup_panicknob and create a/proc/sys/kernel/hardlockup_panicknob.Signed-off-by Don Zickus <[email protected]>--
V2 - wrap the sysctl variable withCONFIG_HARDLOCKUP_DETECTOR(kbuid bot)--- Documentation/lockup-watchdogs.txt | 5 +++-- include/linux/sched.h | 1 + kernel/sysctl.c | 11 +++++++++++ kernel/watchdog.c | 2 +- 4 files changed, 16 insertions(+), 3 deletions(-)Documentation/lockup-watchdogs.txt +3
-2@@ -20,8 +20,9 @@ kernel mode for more than 10 seconds (see "Implementation" below for details), without letting other interrupts have a chance to run. Similarly to the softlockup case, the current stack trace is displayed upon detection and the system will stay locked up unless the default -behavior is changed, which can be done through a compile time knob, -"BOOTPARAM_HARDLOCKUP_PANIC", and a kernel parameter, "nmi_watchdog" +behavior is changed, which can be done through a sysctl, +'hardlockup_panic', a compile time knob, "BOOTPARAM_HARDLOCKUP_PANIC", +and a kernel parameter, "nmi_watchdog" (see "Documentation/kernel-parameters.txt" for details). The panic option can be used in combination with panic_timeout (thisinclude/linux/sched.h +1
-0@@ -384,6 +384,7 @@ extern int proc_dowatchdog_thresh(struct ctl_table *table, int write,void __user *buffer, size_t *lenp, loff_t *ppos);extern unsigned int softlockup_panic; +extern unsigned int hardlockup_panic;void lockup_detector_init (void );#else static inline void touch_softlockup_watchdog (void )kernel/sysctl.c +11
-0@@ -887,6 +887,17 @@ static struct ctl_table kern_table[] = { .extra1 = &zero, .extra2 = &one, }, +#ifdef CONFIG_HARDLOCKUP_DETECTOR + { + .procname = "hardlockup_panic", + .data = &hardlockup_panic, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = &zero, + .extra2 = &one, + }, +#endif #ifdef CONFIG_SMP { .procname = "softlockup_all_cpu_backtrace",kernel/watchdog.c +0
-0
kernel/watchdog.c static unsigned long soft_lockup_nmi_warn; · line 118
Quoted 8 lines
kernel/watchdog.c +1
-1@@ -112,7 +112,7 @@ static unsigned long soft_lockup_nmi_warn;* Should we panic when a soft-lockup or hard-lockup occurs: */ #ifdef CONFIG_HARDLOCKUP_DETECTOR -static int hardlockup_panic = +unsigned int __read_mostly hardlockup_panic =CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE ;static unsigned long hardlockup_allcpu_dumped;/*