linux-kernel - Re: [PATCH v3 0/2] watchdog: allow setting deadline for opening /dev/watchdogN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1a8dd51c-451f-604f-ec21-c8de46533564@prevas.dk>
Date:   Mon, 2 Jan 2017 09:04:30 +0100
From:   Rasmus Villemoes <rasmus.villemoes@...vas.dk>
To:     <linux-watchdog@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC:     Guenter Roeck <linux@...ck-us.net>,
        Sylvain Lemieux <slemieux.tyco@...il.com>
Subject: Re: [PATCH v3 0/2] watchdog: allow setting deadline for opening
 /dev/watchdogN

On 2016-12-14 14:37, Rasmus Villemoes wrote:

> If a watchdog driver tells the framework that the device is running,
> the framework takes care of feeding the watchdog until userspace opens
> the device. If the userspace application which is supposed to do that
> never comes up properly, the watchdog is fed indefinitely by the
> kernel. This can be especially problematic for embedded devices.
>
> These patches allow one to set a maximum time for which the kernel
> will feed the watchdog, thus ensuring that either userspace has come
> up, or the board gets reset.

Ping.

Rasmus