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, 25 May 2007 00:00:17 +0200 From: Pavel Machek <pavel@....cz> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Romano Giannetti <romanol@...omillas.es>, Chris Wright <chrisw@...s-sol.org>, Chuck Ebbert <cebbert@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, stable@...nel.org, Justin Forbes <jmforbes@...uxtx.org>, Zwane Mwaikambo <zwane@....linux.org.uk>, Theodore Ts'o <tytso@....edu>, Randy Dunlap <rdunlap@...otime.net>, Dave Jones <davej@...hat.com>, Chuck Wolber <chuckw@...ntumlinux.com>, Chris Wedgwood <reviews@...cw.f00f.org>, Michael Krufky <mkrufky@...uxtv.org>, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, "Rafael J. Wysocki" <rjw@...k.pl> Subject: Re: pcmcia resume 60 second hang. Re: [patch 00/69] -stable review Hi! > > Well. we'd like to present hardware in working state as soon as we > > resume (if eth0 was there before resume, it should be there after > > resume. not 3 seconds after resume); so if someone needs to load the > > firmware, they should just store it in the kernel memory, and load it > > during boot or during (very early) suspend. > > Equally arguably, we should just have a "resume_late()" call that can be > used to do this after everything is up and running. Yes, we can do that. But userland will see devices "not there" for a few seconds after boot. ...that is ugly, but we can survive it for ethernet cards etc... but it will be really fatal for any block device. Pcmcia block devices exist, so I do not think we can do that. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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