| 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
| ||
|
Message-Id: <201106241655.03637.arnd@arndb.de> Date: Fri, 24 Jun 2011 16:55:03 +0200 From: Arnd Bergmann <arnd@...db.de> To: Mark Lord <kernel@...savvy.com> Cc: Wim Van Sebroeck <wim@...ana.be>, Alan Cox <alan@...rguk.ukuu.org.uk>, LKML <linux-kernel@...r.kernel.org>, Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org> Subject: Re: [PATCH 7/10 v2] Generic Watchdog Timer Driver On Thursday 23 June 2011 16:13:29 Mark Lord wrote: > On 11-06-22 04:13 PM, Wim Van Sebroeck wrote: > > > > This is another tricky thing were developers will always discuss about. > > What you don't want to happen is that the watchdog reboots your system when it does > > an fsck at bootup (for instance because the system rebooted by the watchdog and left > > the filesystem in a dirty state...). > > > > So it's more complex if you look at the overal system... > > Sure, but that's got little to do with wanting a kernel parameter to OPTIONALLY > enable a hardware watchdog timer at boot. > > Filesystem checks are a separate issue, easily worked around in practice. I agree, it's nice to give system integrators the option to enable the watchdog very early, the problems that Wim mentioned need to be solved in user space but are not a serious limitation. Arnd -- 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/
Powered by blists - more mailing lists