linux-kernel - Re: [PATCH] watchdog: add a parameter for stop wdt before register

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] [day] [month] [year] [list]

Message-ID: <20140116015233.GC3807@dhcp-16-126.nay.redhat.com>
Date:	Thu, 16 Jan 2014 09:52:33 +0800
From:	Dave Young <dyoung@...hat.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>, wim@...ana.be,
	dzickus@...hat.com, bhe@...hat.com, linux-watchdog@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] watchdog: add a parameter for stop wdt before register

On 01/15/14 at 11:55am, Vivek Goyal wrote:
> On Wed, Jan 15, 2014 at 12:15:56PM +0000, One Thousand Gnomes wrote:
> > > watchdog and crash dump really conflicts to some degree, from the watchdog
> > > point of view it can reboot system whhen kdump kernel hangs. But from kdump
> > > point of view it want ensure saving the vmcore for later debugging.
> > > 
> > > Maybe we can only select only one in this case.
> > 
> > You want to be able to make a decision at runtime which to use.
> > 
> > > > - if it can be stopped, you can open and stop it
> > > 
> > > For the last one since crashing happens we have no chance to open and stop.
> > 
> > When you decide you need to set up to catch a core rather than just
> > crash you can open and stop the watchdog (if supported), and you can then
> > set up for a kdump and then at some point later if it crashes capture the
> > dump.
> 
> Disabling watchdog if kdump serice starts will not make many happy. If
> kernel hangs, we don't have a functionality to reboot it.
> 
> What about other idea of keeping watchdog interval long enough that new
> kernel can boot, driver can load and then new driver/user space can
> continue to kick the watchdog. And if second kernel hangs, watchdog will
> reboot the system.

I would agree this way.

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