| 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: <20070704233351.GA2719@elf.ucw.cz> Date: Thu, 5 Jul 2007 01:33:51 +0200 From: Pavel Machek <pavel@....cz> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway Hi! > 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. > > Signed-off-by: Matthew Garrett <mjg59@...f.ucam.org> Sorry, no. * this needs audit of all drivers. Or we can just merge it and then fix all the problems it causes. If you are willing to become suspend maintainer and handle all that mess, perhaps we can do this. * it does not solve FUSE vs. hibernation * it does not solve FUSE vs. suspend-to-both * userspace will now see CPUs going up and down at minimum Now, we want to do something like this long-term, but I do not think we can just remove the freezer like this. 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