Re: [PATCH v9 1/3] watchdog: introduce watchdog.open_timeout commandline parameter

2019-01-29 Thread Rasmus Villemoes
On 29/01/2019 21.35, Rasmus Villemoes wrote: > On 22/01/2019 18.29, Guenter Roeck wrote: >> On Mon, Jan 21, 2019 at 08:45:39PM +, Rasmus Villemoes wrote: >>> >>> static void watchdog_ping_work(struct kthread_work *work) >>> @@ -297,7 +317,7 @@ static int watchdog_stop(struct watchdog_device

Re: [PATCH v9 1/3] watchdog: introduce watchdog.open_timeout commandline parameter

2019-01-29 Thread Rasmus Villemoes
On 22/01/2019 18.29, Guenter Roeck wrote: > On Mon, Jan 21, 2019 at 08:45:39PM +, Rasmus Villemoes wrote: >> The watchdog framework takes care of feeding a hardware watchdog until >> userspace opens /dev/watchdogN. If that never happens for some reason >> (buggy init script, corrupt root filesy

Re: [PATCH v9 1/3] watchdog: introduce watchdog.open_timeout commandline parameter

2019-01-22 Thread Guenter Roeck
On Mon, Jan 21, 2019 at 08:45:39PM +, Rasmus Villemoes wrote: > The watchdog framework takes care of feeding a hardware watchdog until > userspace opens /dev/watchdogN. If that never happens for some reason > (buggy init script, corrupt root filesystem or whatnot) but the kernel > itself is fin

[PATCH v9 1/3] watchdog: introduce watchdog.open_timeout commandline parameter

2019-01-21 Thread Rasmus Villemoes
The watchdog framework takes care of feeding a hardware watchdog until userspace opens /dev/watchdogN. If that never happens for some reason (buggy init script, corrupt root filesystem or whatnot) but the kernel itself is fine, the machine stays up indefinitely. This patch allows setting an upper l