| 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: <20070705000235.GD2719@elf.ucw.cz> Date: Thu, 5 Jul 2007 02:02:35 +0200 From: Pavel Machek <pavel@....cz> To: Miklos Szeredi <miklos@...redi.hu> Cc: oliver@...kum.org, linux-pm@...ts.linux-foundation.org, benh@...nel.crashing.org, nigel@...el.suspend2.net, mjg59@...f.ucam.org, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway Hi! > > > I don't claim to know anything about how STR or hibernate works, but > > > neither seem to have any problem with I/O on the fuse device "racing" > > > with them. > > > > The problem is not with fuse. The problem is generic in nature. > > > > If you remove the freezer, user space remains active until the last CPU > > goes into suspend. It can do syscalls. Or do you know a clean way to exempt > > only the tasks fuse might use? > > You are talking about hibernate, right? Suspending (to ram) is > instantaneous, in that _after_ suspend no CPU is active obviously. No, suspend to ram is not instantaneous. We may have 16 cpus, and we may have 250 disks that need to be spun down. That takes time, and is really not atomic operation. 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