| 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: <CACVXFVMKzYbELKYsQSV55kqCTTVtez8SDKSrwJn55iszmjXrOw@mail.gmail.com> Date: Thu, 26 Jul 2012 23:15:37 +0800 From: Ming Lei <ming.lei@...onical.com> To: Borislav Petkov <bp@...64.org> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH 09/13] driver core: firmware loader: store firmware name into devres list On Thu, Jul 26, 2012 at 12:15 AM, Borislav Petkov <bp@...64.org> wrote: > On Wed, Jul 25, 2012 at 01:00:09AM +0800, Ming Lei wrote: >> This patch will store firmware name into devres list of the device >> which is requesting firmware loading, so that we can implement >> auto cache firmware for devices in need. > > Stupid question: does this mean that once the firmware name is in the > devres list, it is being cached automatically and device drivers which > don't want that need to explicitly uncache it? Both the auto cache and auto uncache actions are not triggered by device driver, and will be triggered by some system state, for example, in 13/13, you will find the cache is done before system suspend and the uncache is done after system resume. If device drivers want to cache its firmware explicitly, they have to uncache it explicitly too, see cache_firmware/uncache_firmware in 7/13. Thanks -- Ming Lei -- 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