linux-kernel - Re: Bootup support for watchdog with short timeout (touch_nmi

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:	Tue, 30 Oct 2007 08:51:08 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Josh Boyer <jwboyer@...il.com>
Cc:	Stefan Roese <stefan.roese@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Bootup support for watchdog with short timeout (touch_nmi_watchdog()?)

On Mon, Oct 29, 2007 at 09:54:54PM -0500, Josh Boyer wrote:
> To some degree, it's configurable.  But the generic question still
> stands.  It seems like a decent idea to me.  Making touch_watchdog (or
> whatever it winds up being called) nice across arches might be fun.

It always seemed to me that it was userspace that should poke the
watchdog as an indication user space still works on the system.  That's
how my watchdogs are managed.  I do initialize them in the boot loader
with a 3 minute timeout which is more than long enough for the system to
boot, load the driver and change the timeout to 60 seconds or whatever
I want at runtime and start the watchdog daemon.

If the kernel hangs at initializing some driver, I do NOT want the
kernel to automatically be poking the watchdog.  I want it to time out
so to me the kernel should not be able to kick the watchdog at all by
itself.

--
Len Sorensen
-
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/