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] [day] [month] [year] [list]
Message-ID: <31d75b51-6cd6-9029-40a5-fec631e110bf@prevas.dk>
Date:   Wed, 1 May 2019 06:32:02 +0000
From:   Rasmus Villemoes <rasmus.villemoes@...vas.dk>
To:     "Jerry.Hoemann@....com" <Jerry.Hoemann@....com>
CC:     "linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Jonathan Corbet <corbet@....net>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Esben Haabendal <esben@...bendal.dk>,
        "martin@...deboll.net" <martin@...deboll.net>,
        Rasmus Villemoes <Rasmus.Villemoes@...vas.se>
Subject: Re: [PATCH v9 0/3] watchdog: allow setting deadline for opening
 /dev/watchdogN

On 01/05/2019 02.05, Jerry Hoemann wrote:
> On Mon, Jan 21, 2019 at 08:45:38PM +0000, Rasmus Villemoes wrote:
>>
>> These patches allow one to set a maximum time for which the kernel
>> will feed the watchdog,
> 
> Rasmus,
> 
> Sorry if I missed it, but are you still looking into adding
> this feature? 

I am, and still intend to get around to it when I get some idle cycles.

I was thinking it might also be useful with
> kdump when a watchdog was running in the first kernel.
> 
> After a panic if kdump is configured, the system will boot the
> crash kernel.  If a watchdog was running in the first kernel
> it would still running in the crash kernel environment.
> 
> Some of the drivers on HPE systems take a non-trivial amount of time
> to reset during the crash kernel boot, so it would be good to have
> the core pet the watchdog until user space is ready.  But as the
> crash kernel environment has its issues,  we really don't want
> the core to ping the watchdog indefinitely.

Thanks, it's great to hear that others would also be interested in this.
This will move it up a few places on my todo list. I'll try to remember
to add you to the cc list.

Thanks,
Rasmus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ