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: <20110330161419.GB28252@pulham.picochip.com>
Date:	Wed, 30 Mar 2011 17:14:19 +0100
From:	Jamie Iles <jamie@...ieiles.com>
To:	Daniel Walker <dwalker@...o99.com>
Cc:	Jeff Ohlstein <johlstei@...eaurora.org>,
	Bryan Huntsman <bryanh@...eaurora.org>,
	David Brown <davidb@...eaurora.org>,
	linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Russell King <linux@....linux.org.uk>,
	Stepan Moskovchenko <stepanm@...eaurora.org>,
	Gregory Bean <gbean@...eaurora.org>,
	Abhijeet Dharmapurikar <adharmap@...eaurora.org>
Subject: Re: [PATCH] msm: watchdog: support watchdog on 8x60 and 8960

On Wed, Mar 30, 2011 at 09:03:26AM -0700, Daniel Walker wrote:
> On Tue, 2011-03-29 at 21:40 -0700, Jeff Ohlstein wrote:
> > Daniel Walker wrote:
> > > Are you saying this is mostly a debugging facility ? The interrupts off
> > > thing I can see as just debugging, but I don't understand the bus
> > > lockups part.
> > >   
> > 
> > It isn't just a debugging facility. It is still beneficial to the end user
> > in that it restarts the system if there is a bus lockup or a faulty 
> > interrupt
> > handler in a rarely used codepath. This is better than the alternative 
> > of draining
> > the battery and turning off. We want this to be turned on independent of 
> > what userspace
> > one is using, unless they explicitly turn it off themselves.
> 
> It doesn't sound too different that all the other watchdogs in
> drivers/watchdog/ .. Your just detecting lockups right?

There are some watchdogs in there such as 
drivers/watchdog/at91sam9_wdt.c that can't be stopped once enabled so 
the driver sets up a soft timer in the kernel that kicks the watchdog to 
prevent the system rebooting.

With this approach you could have the watchdog always enabled and being 
kicked even if the userspace daemon wasn't running, but with the 
flexibility of kicking it from userspace if you wanted.

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