linux-kernel - Re: [RFC] [PATCH 8/10] Generic Watchdog Timer Driver

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]

Date:	Thu, 24 Feb 2011 09:05:24 +0100
From:	Alexander Stein <alexander.stein@...tec-electronic.com>
To:	Wim Van Sebroeck <wim@...ana.be>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH 8/10] Generic Watchdog Timer Driver

On Wednesday 23 February 2011, 21:44:36 Wim Van Sebroeck wrote:
> commit 5752d34c58c9b654c2fa753b94acc67602836420
> Author: Wim Van Sebroeck <wim@...ana.be>
> Date:   Sun Jul 18 10:51:52 2010 +0000
> 
>     watchdog: WatchDog Timer Driver Core - Part 8
> 
>     Add support for the nowayout feature to the
>     WatchDog Timer Driver Core framework.
>     This feature prevents the watchdog timer from being
>     stopped.
> 
>     Signed-off-by: Alan Cox <alan@...rguk.ukuu.org.uk>
>     Signed-off-by: Wim Van Sebroeck <wim@...ana.be>
> 
> [...]
> diff --git a/Documentation/watchdog/watchdog-kernel-api.txt
> b/Documentation/watchdog/watchdog-kernel-api.txt index 036c30f..91c4299
> 100644
> --- a/Documentation/watchdog/watchdog-kernel-api.txt
> +++ b/Documentation/watchdog/watchdog-kernel-api.txt
> @@ -57,8 +57,8 @@ It contains following fields:
>    WDIOF_* status bits).
>  * status: this field contains a number of status bits that give extra
>    information about the status of the device (Like: is the watchdog timer
> -  running/active, is the device opened via the /dev/watchdog interface or
> not, -  ...)
> +  running/active, is the nowayout bit set, is the device opened via
> +  the /dev/watchdog interface or not, ...)
> 
>  The list of watchdog operations is defined as:
> 
> @@ -123,6 +123,8 @@ bit-operations. The status bit's that are defined are:
>    is active or not. When the watchdog is active after booting, then you
> should set this status bit (Note: when you register the watchdog timer
> device with this bit set, then opening /dev/watchdog will skip the start
> operation) +* WDOG_NO_WAY_OUT: this bit stores the nowayout setting for
> the watchdog. +  If this bit is set then the watchdog timer will not be
> able to stop. * WDOG_DEV_OPEN: this status bit shows whether or not the
> watchdog device was opened via /dev/watchdog.
>    (This bit should only be used by the WatchDog Timer Driver Core).
> @@ -135,6 +137,6 @@ bit-operations. The status bit's that are defined are:
>    has been sent (so that we can support the magic close feature).
>    (This bit should only be used by the WatchDog Timer Driver Core).
> 
> -Note: The WatchDog Timer Driver Core supports the magic close feauture. To
> use -the magic close feauture you must set the WDIOF_MAGICCLOSE bit in the
> options -field of the watchdog's info structure.
> +Note: The WatchDog Timer Driver Core supports the nowayout feature and the
> +magic close feauture. To use the magic close feauture you must set the
                  ^                                 ^
small typos here

Alexander
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/