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: <A874F61F95741C4A9BA573A70FE3998F82E4BD12@DQHE02.ent.ti.com>
Date:	Mon, 15 Apr 2013 00:43:31 +0000
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Guenter Roeck <linux@...ck-us.net>
CC:	"wim@...ana.be" <wim@...ana.be>,
	"linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] watchdog: introduce new watchdog AUTOSTART option

Hi Guenter

> I really don't like that idea. It defeats a significant part of the
> purpose
> for having a watchdog, which is to prevent user-space hangups.
> 
> To make this a driver option is even more odd - it forces every user of
> this
> driver to use it in-kernel only, and makes /dev/watchdog quite useless.
> 
> I mean, really, if you have such a watchdog, what is the point of using
> the
> watchdog infrastructure in the first place ? Just make it a kernel
> thread or
> timer-activated platform code which pings your watchdog once in a while.
> No
> need to get the watchdog infrastructure involved in the first place.
> 
> Am I missing something ?

I wanted to enable the watchdog timer without the watchdog application for
making sure the system alive.
However, I think I misunderstood the purpose of the watchdog driver.
The watchdog is for detecting user-space hangups rather than kernel stall.
Is it correct? If yes, this patch is totally wrong.

Thanks!

Milo

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ