linux-kernel - Re: [PATCH] iTCO_wdt: Don't stop on shutdown with nowayout

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:	Wed, 24 Feb 2010 07:25:42 +0100
From:	Simon Kagstrom <simon.kagstrom@...insight.net>
To:	Pádraig Brady <P@...igBrady.com>
Cc:	linux-kernel@...r.kernel.org, wim@...ana.be, seth.heasley@...el.com
Subject: Re: [PATCH] iTCO_wdt: Don't stop on shutdown with nowayout

On Tue, 23 Feb 2010 16:24:52 +0000
> > +	if (!nowayout)
> > +		iTCO_wdt_stop();
> >   }
> >
> >   #define iTCO_wdt_suspend NULL
> 
> I see the issue, however what happens if you're
> rebooting into a system that doesn't then renable the watchdog.
> I've seen systems where the hardware watchdog is not reset
> during the reboot process, in which case you'll get a
> reboot while running the other system.

Well, in that case I would run without nowayout. I just think the
behavior is a bit strange if the watchdog is turned off at all if we
have nowayout set.

Thanks for your suggestion though!

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