linux-kernel - Re: [PATCH 1/2] watchdog: introduce new watchdog AUTOSTART option

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:	Sun, 14 Apr 2013 19:06:42 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	"Kim, Milo" <Milo.Kim@...com>
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

On Mon, Apr 15, 2013 at 12:43:31AM +0000, Kim, Milo wrote:
> 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.
> 
Correct. After all, if the kernel stalls, user space will stall as well, so by
covering user space it covers both. Covering kernel alone doesn't help much,
since most of the stalls (at least in my experience) happen in user space.

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