| 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: Mon, 20 Feb 2012 11:32:50 +0100 From: "Arend van Spriel" <arend@...adcom.com> To: "Kay Sievers" <kay.sievers@...y.org> cc: "Larry Finger" <Larry.Finger@...inger.net>, LKML <linux-kernel@...r.kernel.org>, driverdevel <devel@...verdev.osuosl.org>, wireless <linux-wireless@...r.kernel.org>, "linux-hotplug@...r.kernel.org" <linux-hotplug@...r.kernel.org> Subject: Re: will these methods work with firmware loading? On 02/20/2012 11:19 AM, Kay Sievers wrote: >> For that >> > problem I would say yes. Also here the problem of handling error flows >> > exist. If the driver is kicked of during boot with a initramfs missing the >> > firmware, should we retry until the real root is mounted? > I don't think so. Drivers are not supposed to know about bootup or > initramfs issues. If they want, they can disable the timeout, and wait > for userspace to handle the request any time later, but they should > not try to be smart here. > > Currently, firmware requests are cancelled if the firmware isn't > found, but that's a userspace issue, and nothing the kernel should try > to work around. I can not agree more. I prefer to keep my driver happily unaware. I will just take the firmware loading away from the module init path and stop worrying about userspace issues ;-) Gr. AvS -- 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