| 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
| ||
|
Message-Id: <1186651290.21247.3.camel@lov.localdomain> Date: Thu, 09 Aug 2007 11:21:30 +0200 From: Kay Sievers <kay.sievers@...y.org> To: Javier Pello <javier.pello@...c.es> Cc: Cornelia Huck <cornelia.huck@...ibm.com>, linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com> Subject: Re: [PATCH] request_firmware: skip timeout if userspace was not notified On Thu, 2007-08-09 at 11:13 +0200, Javier Pello wrote: > On Tue, 07 Aug 2007, Kay Sievers wrote: > > Nope, you would just fulfill in a completely generic way all outstanding > > requests when you are ready. All requests are all nicely grouped and > > visible in sysfs. There would be no need of coding your own device > > specific rebind. No timeout is needed or wanted, all requests would stay > > until userspace has handled them successfully or canceled them. > > If I'm not mistaken, as it is now, requests are not grouped in any way. > The only hint that a firmware loading request is in progress are a couple > of files in the device directory in sysfs. Should I run, at boot, through > all the device directories to check which firmware requests are pending? /sys/class/firmware/* contains all pending requests, no need to search anywhere else. Kay - 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