Hi stable maintainers
Can I get you to consider including
bc137dfdbec2 watchdog: gpio_wdt: set WDOG_HW_RUNNING in gpio_wdt_stop
in -stable? Without that, any (always-running) gpio watchdog effectively fails to honour the magic close feature, causing an unexpected reset shortly after userspace gracefully closes the device.
Anything containing 3c10bbde10 ("watchdog: core: Clear WDOG_HW_RUNNING before calling the stop function") probably needs it (i.e. 4.8+), but at the very least 4.14 and 4.15.
Rasmus
On Sat, Feb 10, 2018 at 10:56:02PM +0100, Rasmus Villemoes wrote:
Hi stable maintainers
Can I get you to consider including
bc137dfdbec2 watchdog: gpio_wdt: set WDOG_HW_RUNNING in gpio_wdt_stop
in -stable? Without that, any (always-running) gpio watchdog effectively fails to honour the magic close feature, causing an unexpected reset shortly after userspace gracefully closes the device.
Anything containing 3c10bbde10 ("watchdog: core: Clear WDOG_HW_RUNNING before calling the stop function") probably needs it (i.e. 4.8+), but at the very least 4.14 and 4.15.
Now queued up, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org