| 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: <20070527204955.GA22202@srcf.ucam.org> Date: Sun, 27 May 2007 21:49:56 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: 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 10:31:53PM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki <rjw@...k.pl> > > Use a hibernation and suspend notifier to disable the firmware requesting > mechanism before a hibernation/suspend and enable it after the operation. This avoids the problem of .resume methods calling userspace while userspace is frozen and a resulting hang, but does it actually result in the drivers beginning to work again? If we remove process freezing in STR, this should just work[1] without the need to complicate things. On the other hand, if we don't want to support these functions in the suspend and resume methods we could just audit the kernel and remove them all. -- 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