| 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 17:19:39 +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 > I am not really happy about the watchdog device appearing and disappearing > dynamically. This wreaks havoc with any standard watchdog application. Any software that doesn't handle this has been broken for over fifteen years. We have hotplug PCI and we have PCI watchdog card support. This isn't a new behaviour to anyone outside the embedded single board space. > Isn't there a better way to handle this ? How about just registering the > watchdog device and return an error in the access functions if it is disabled ? 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. 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