mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-09-18 22:14:16 +00:00
watchdog: iTCO_wdt: Update the heartbeat value after clamping timeout
When executing "modprobe iTCO_wdt heartbeat=700", the user-specified 'heartbeat' parameter exceeds the valid range, the driver clamps the timeout to default 30s but fails to update the logged 'heartbeat' value, resulting in misleading log output: iTCO_wdt iTCO_wdt: timeout value out of range, using 30 iTCO_wdt iTCO_wdt: initialized. heartbeat=700 sec (nowayout=0) After validating the range, update the 'heartbeat' value with the clamped timeout value to ensure that log messages accurately reflect the actual runtime parameters. Signed-off-by: Ziyan Fu <fuzy5@lenovo.com> Reviewed-by: Wim Van Sebroeck <wim@linux-watchdog.org> Link: https://lore.kernel.org/r/20250429102533.11886-1-13281011316@163.com Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
This commit is contained in:
parent
535d1784d8
commit
158f9f2f71
1 changed files with 1 additions and 0 deletions
|
@ -580,6 +580,7 @@ static int iTCO_wdt_probe(struct platform_device *pdev)
|
|||
iTCO_wdt_set_timeout(&p->wddev, WATCHDOG_TIMEOUT);
|
||||
dev_info(dev, "timeout value out of range, using %d\n",
|
||||
WATCHDOG_TIMEOUT);
|
||||
heartbeat = WATCHDOG_TIMEOUT;
|
||||
}
|
||||
|
||||
watchdog_stop_on_reboot(&p->wddev);
|
||||
|
|
Loading…
Add table
Reference in a new issue