| 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: Sun, 27 May 2007 23:04:12 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Kay Sievers <kay.sievers@...y.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, pm list <linux-pm@...ts.linux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Nigel Cunningham <nigel@...el.suspend2.net>, Pavel Machek <pavel@....cz>, Alan Stern <stern@...land.harvard.edu>, Oliver Neukum <oliver@...kum.org> Subject: Re: [RFC][PATCH -mm 3/3] PM: Disable _request_firmware before hibernation/suspend On Sun, May 27, 2007 at 11:49:30PM +0200, Kay Sievers wrote: > What exactly is the problem we see here? The timeout of the firmware loader? > What goes wrong with frozen userspace, usually there is only a netlink > message sent from the kernel, which should be received and handled > just fine when userspace is running again. Driver calls request_firmware in the resume method. The userspace helper can't be run because it's been frozen, so the firmware never gets loaded and the call times out. The driver then fails to resume. While all this is happening, the rest of the kernel is blocking on that resume method. The firmware can be loaded once userspace has been started again, but by that time the driver has given up. -- Matthew Garrett | mjg59@...f.ucam.org - 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