linux-kernel - Re: watchdog start on restart

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: <6dd97c08809d576136d474f4b3f3b045a03634bb.camel@yadro.com>
Date:   Thu, 3 Sep 2020 13:19:28 +0300
From:   Ivan Mikhaylov <i.mikhaylov@...ro.com>
To:     Christophe Leroy <christophe.leroy@...roup.eu>
CC:     Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Guenter Roeck <linux@...ck-us.net>,
        <linux-watchdog@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: watchdog start on restart

On Wed, 2020-09-02 at 15:19 +0200, Christophe Leroy wrote:
 
> Isn't it the default expected behaviour for a watchdog ?

It depends on hardware and system requirements. You may have not just one
watchdog device.

> "stop watchdog on restart" is there to keep things under control during 
> a wanted machine reboot/restart, while still having the watchdog do its 
> job on an unexpected restart.

Yes, that's correct.

> What would be the advantage of an ioctl() compared to the existing way ?

You can control stop/start at any moment for any number of watchdog devices.

Thanks.