| 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: Wed, 04 Jul 2007 07:16:24 +1000 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: "Rafael J. Wysocki" <rjw@...k.pl> 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 On Tue, 2007-07-03 at 15:08 +0200, Rafael J. Wysocki wrote: > On Tuesday, 3 July 2007 07:51, Benjamin Herrenschmidt wrote: > > On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote: > > > Suspend to RAM on a machine with / on a fuse filesystem turns out to be > > > a screaming nightmare - either the suspend fails because syslog (for > > > instance) can't be frozen, or the machine deadlocks for some other > > > reason I haven't tracked down. We could "fix" fuse, or alternatively we > > > could do what we do for suspend to RAM on other platforms (PPC and APM) > > > and just not use the freezer. > > > > The main reason for deadlocks is because we do a sys_sync() after the > > freeze, which we shouldn't do. > > So why don't we remove the sys_sync() from freeze_processes() instead? Or rather, move it to before freeze_processes() so that you get at least some level of sync'ing just in case you never wake up. Not perfect (things may still get dirty) but it will help the immediate issue. Ben. - 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