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: Tue, 3 Jul 2007 10:20:13 +0200 From: Oliver Neukum <oliver@...kum.org> To: Romano Giannetti <romanol@...omillas.es> Cc: Matthew Garrett <mjg59@...f.ucam.org>, linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway Am Dienstag, 3. Juli 2007 schrieb Romano Giannetti: > On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote: > > or alternatively we could do what we do for suspend to RAM on other > > platforms (PPC and APM) and just not use the freezer. > > As a data point, I am running with this patch on top of 2.6.21.2 the > last 3+ weeks, with an average of 5/6 STR cycles a day, and had no > problems at all. (Sony vaio pcg-fx701). Just normal work, I didn't try > to stress the thing, but I have quite a few times suspended/resumed over > a big compile without a glitch. > > What are the risks of this patch supposed to be? You did this test only while stressing normal block devices. Try provoking races in character devices. Regards Oliver - 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