linux-kernel - Re: request_firmware vs. resume (was Re: [PATCH] bnx2

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jul 2008 17:20:24 -0400
From:	Theodore Tso <tytso@....edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Pavel Machek <pavel@...e.cz>, David Miller <davem@...emloft.net>,
	alan@...rguk.ukuu.org.uk, mchan@...adcom.com, dwmw2@...radead.org,
	bastian@...di.eu.org, linux-kernel@...r.kernel.org
Subject: Re: request_firmware vs. resume (was Re: [PATCH] bnx2 - use
	request_firmware())

On Wed, Jul 09, 2008 at 11:13:54PM +0200, Rafael J. Wysocki wrote:
> > Be careful about request_firmware. Doing it right w.r.t.
> > suspend/resume is quite tricky: you have to load it from userspace
> > before kernel starts, so that you can use it during resume...
> 
> Rather, you have to cache it in memory before your ->suspend() is invoked.

Translation: so much for saving "non-swappable kernel memory".
Unless, of course we add a pre-suspend hook.  (Which doesn't exist
yet, AFAICT from a quick perusal of Documentation/power/devices.txt.)


     	    	   	 	    - Ted
--
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/