| 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
| ||
|
Date: Fri, 18 Dec 2015 18:14:12 +0000 From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk> To: Guenter Roeck <linux@...ck-us.net> Cc: Tomas Winkler <tomas.winkler@...el.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Wim Van Sebroeck <wim@...ana.be>, Alexander Usyskin <alexander.usyskin@...el.com>, linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [char-misc-next v2 7/7] watchdog: mei_wdt: re-register device on event > > That breaks the existing behaviour of hot pluggable watchdog interfaces > > and is different to just about any other device in the kernel. Today with > > any desktop or server distribution you can already trivially arrange for > > watchdog daemons to start at the point a watchdog is detected dynamically. > > > > Ok, you have a point. Wonder if any distributions are doing that, though. > Any idea ? I don't know for any of the out of the box mainstream ones. There is a second problem if you register the watchdog but don't actually have it enabled. Consider the case where a user has the mei watchdog disabled and a more advanced watchdog card plugged in - in that case the naïvely implemented existing watchdog app may bind to the non-functional watchdog, not the correct one. Alan -- 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