watchdog: pretimeout: Add "dump" pretimeout governor
PATCH 1/1 watchdog: pretimeout: Add "dump" pretimeout governor
Add a new "dump" pretimeout governor that triggers a backtrace of all CPUs (via trigger_all_cpu_backtrace()) to the kernel log buffer. This provides diagnostic information right before the hardware watchdog fires.
In addition, update the WATCHDOG_PRETIMEOUT_GOV_SEL Kconfig logic to fall back to the "panic" governor only when both "noop" and "dump" governors are disabled.
---
Alternatives considered:
We can also introduce some options and put trigger_all_cpu_backtrace() into the existing "noop" governor.
--- drivers/watchdog/Kconfig | 19 ++++++++++- drivers/watchdog/Makefile | 1 + drivers/watchdog/pretimeout_dump.c | 45 ++++++++++++++++++++++++++ drivers/watchdog/watchdog_pretimeout.h | 4 ++- 4 files changed, 67 insertions(+), 2 deletions(-) create mode 100644 drivers/watchdog/pretimeout_dump.c
drivers/watchdog/Kconfig +18 -1
@@ -93,10 +93,19 @@ config WATCHDOG_PRETIMEOUT_GOV_SEL tristate depends on WATCHDOG_PRETIMEOUT_GOV default m - select WATCHDOG_PRETIMEOUT_GOV_PANIC if WATCHDOG_PRETIMEOUT_GOV_NOOP=n + select WATCHDOG_PRETIMEOUT_GOV_PANIC if \ + WATCHDOG_PRETIMEOUT_GOV_NOOP=n && WATCHDOG_PRETIMEOUT_GOV_DUMP=n if WATCHDOG_PRETIMEOUT_GOV +config WATCHDOG_PRETIMEOUT_GOV_DUMP + tristate "Dump watchdog pretimeout governor" + depends on WATCHDOG_CORE + default WATCHDOG_CORE + help + Dump watchdog pretimeout governor, all cpu backtrace is + added to kernel log buffer. + config WATCHDOG_PRETIMEOUT_GOV_NOOP tristate "Noop watchdog pretimeout governor" depends on WATCHDOG_CORE
@@ -121,6 +130,14 @@ choice The governor takes its action, if a watchdog is capable to report a pretimeout event. +config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_DUMP + bool "dump" + depends on WATCHDOG_PRETIMEOUT_GOV_DUMP + help + Use dump watchdog pretimeout governor by default. If dump + governor is selected by a user, dump all cpu backtrace to + the kernel log buffer and don't do any system changes. + config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP bool "noop" depends on WATCHDOG_PRETIMEOUT_GOV_NOOP
drivers/watchdog/Makefile +1 -0
@@ -11,6 +11,7 @@ watchdog-objs += watchdog_core.o watchdog_dev.o watchdog-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV) += watchdog_pretimeout.o watchdog-$(CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT) += watchdog_hrtimer_pretimeout.o +obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_DUMP) += pretimeout_dump.o obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP) += pretimeout_noop.o obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC) += pretimeout_panic.o
drivers/watchdog/pretimeout_dump.c new file +45 -0
45 lines not on this page · raw message
drivers/watchdog/watchdog_pretimeout.h +3 -1
@@ -24,7 +24,9 @@ int watchdog_pretimeout_governor_get(struct watchdog_device *wdd, char *buf);int watchdog_pretimeout_governor_set (struct watchdog_device *wdd,const char *buf); -#if IS_ENABLED (CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP ) +#if IS_ENABLED (CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_DUMP ) +#define WATCHDOG_PRETIMEOUT_DEFAULT_GOV "dump" +#elif IS_ENABLED (CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP )#define WATCHDOG_PRETIMEOUT_DEFAULT_GOV "noop"#elif IS_ENABLED (CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC )#define WATCHDOG_PRETIMEOUT_DEFAULT_GOV "panic"
Signature · 1 line
2.55.0.rc2.803.g1fd1e6609c-goog
[email protected]
AI reviewThank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
New issues:
- [Low] Compiling the new 'dump' pretimeout governor as a loadable module causes a modpost build failure because trigger_all_cpu_backtrace() relies on an unexported symbol.
Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but unregistering the default watchdog pretimeout governor leaves dangling pointers in default_gov and device structs, leading to a Use-After-Free (UAF) upon the next pretimeout event or sysfs read. --
--- Patch [1]: [PATCH] watchdog: pretimeout: Add "dump" pretimeout governor --- commit dc8900cef0c7ac20c37ff84ef6166ddde30f5da7
Author: Tzung-Bi Shih <[email protected]>
watchdog: pretimeout: Add "dump" pretimeout governor
This patch adds a new "dump" pretimeout governor that triggers a backtrace of all CPUs to the kernel log buffer before the watchdog fires. It also updates the Kconfig logic to fall back to the "panic" governor only when both "noop" and "dump" governors are disabled.
Quoted 4 lines
drivers/watchdog/Kconfig +0
-0
[ ... ]
drivers/watchdog/Kconfig config WATCHDOG_PRETIMEOUT_GOV_SEL · line 97
Quoted 6 lines
drivers/watchdog/Kconfig +2
-0@@ -93,10 +93,19 @@ config WATCHDOG_PRETIMEOUT_GOV_SEL if WATCHDOG_PRETIMEOUT_GOV +config WATCHDOG_PRETIMEOUT_GOV_DUMP + tristate "Dump watchdog pretimeout governor"
[Severity: Low]
Will this fail to build if compiled as a module?
When CONFIG_WATCHDOG_PRETIMEOUT_GOV_DUMP=m, trigger_all_cpu_backtrace() can rely on unexported architecture-specific functions (such as arch_trigger_cpumask_backtrace() on x86, ARM, and ARM64), which causes a modpost build failure.
Quoted 3 lines
drivers/watchdog/Kconfig +3
-0+ depends on WATCHDOG_CORE + default WATCHDOG_CORE + help
[ ... ]
Quoted 5 lines
drivers/watchdog/pretimeout_dump.c new file +0
-0
[ ... ]
drivers/watchdog/pretimeout_dump.c line 39
Quoted 4 lines
drivers/watchdog/pretimeout_dump.c new file +4
-0+static void __exit watchdog_gov_dump_unregister(void) +{ +watchdog_unregister_governor (&watchdog_gov_dump); +}
[Severity: High]
This is a pre-existing issue, but does unregistering the default watchdog pretimeout governor leave dangling pointers?
If this module is set as the default governor and then unloaded, watchdog_unregister_governor() attempts to reset the active governors:
list_for_each_entry(p, &pretimeout_list, entry)
if (p->wdd->gov == gov)
p->wdd->gov = default_gov;If the unregistered governor is the default governor, default_gov equals gov. This leaves p->wdd->gov pointing to the unloaded module's struct.
Could this lead to a use-after-free upon the next pretimeout event or sysfs read?
Quoted 2 lines
drivers/watchdog/pretimeout_dump.c new file +2
-0+module_init (watchdog_gov_dump_register); +module_exit (watchdog_gov_dump_unregister);
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Quoted 17 lines · On Tue, Jul 07, 2026 at 08:02:24AM +0000, [email protected] wrote:
Quoted 4 lines
drivers/watchdog/Kconfig +0
-0[ ... ]
drivers/watchdog/Kconfig config WATCHDOG_PRETIMEOUT_GOV_SEL · line 97
Quoted 6 lines
drivers/watchdog/Kconfig +2
-0@@ -93,10 +93,19 @@ config WATCHDOG_PRETIMEOUT_GOV_SEL if WATCHDOG_PRETIMEOUT_GOV +config WATCHDOG_PRETIMEOUT_GOV_DUMP + tristate "Dump watchdog pretimeout governor"[Severity: Low]
Will this fail to build if compiled as a module?
Quoted 4 lines
When
CONFIG_WATCHDOG_PRETIMEOUT_GOV_DUMP=m,trigger_all_cpu_backtrace()can rely on unexported architecture-specific functions (such asarch_trigger_cpumask_backtrace()on x86, ARM, and ARM64), which causes a modpost build failure.
Use a bool instead in v2 [1].
[1] https://lore.kernel.org/all/[email protected]
Quoted 24 lines
Quoted 5 lines
drivers/watchdog/pretimeout_dump.c new file +0
-0[ ... ]
drivers/watchdog/pretimeout_dump.c line 39
Quoted 4 lines
drivers/watchdog/pretimeout_dump.c new file +4
-0+static void __exit watchdog_gov_dump_unregister(void) +{ +watchdog_unregister_governor (&watchdog_gov_dump); +}[Severity: High]
This is a pre-existing issue, but does unregistering the default watchdog pretimeout governor leave dangling pointers?If this module is set as the default governor and then unloaded,
watchdog_unregister_governor()attempts to reset the active governors:list_for_each_entry(p, &pretimeout_list, entry) if (p->wdd->gov == gov) p->wdd->gov = default_gov;
Quoted 5 lines
If the unregistered governor is the default governor,
default_govequals gov. This leavesp->wdd->govpointing to the unloaded module's struct.Could this lead to a use-after-free upon the next pretimeout event or sysfs read?
Proposed a fix in [2].