linux-kernel - Re: w83697hf_wdt.c stops watchdog on load

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 12 Mar 2008 13:00:36 +0100
From:	Samuel Tardieu <sam@...1149.net>
To:	Pádraig Brady <P@...igBrady.com>
Cc:	Wim Van Sebroeck <wim@...ana.be>, junker@...uras.de,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: w83697hf_wdt.c stops watchdog on load

On 12/03, Pádraig Brady wrote:

| When doing this it would be useful to print a warning iif the watchdog
| was running.

Agreed.

| p.s. I'm still not sure it should default to turning off.
| It would be unusual for userspace to take over 60s to _start_
| If that was the case then the user shouldn't enable the watchdog in the
| BIOS at all.

Most users I know using this watchdog are using it on an hosted
dedicated server, for which the boot messages are not available.
Aborting because of the watchdog triggering during fsck would not be
easily spottable. I prefer to err on the safe side from the user point
of view, even though I guess what you see as being "on the safe side"
would be to keep the watchdog enabled :)

  Sam

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