| 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: <18059.21555.317415.928416@cargo.ozlabs.ibm.com> Date: Wed, 4 Jul 2007 18:02:59 +1000 From: Paul Mackerras <paulus@...ba.org> To: Miklos Szeredi <miklos@...redi.hu> Cc: oliver@...kum.org, benh@...nel.crashing.org, mjg59@...f.ucam.org, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway Miklos Szeredi writes: > That's weird, I never had a suspend problem due to a fuse mount, > though I have them all the time. And I suspect, that even the sync() Well, I don't either, because we don't freeze processes on powerbooks. But I have heard that other people have problems with suspending with a fuse filesystem mounted. Maybe the difference is whether or not the filesystem is writable? > thing that suspend does is not the real cause, because sync() actually > does nothing in fuse filesystems. It's not the filesystem sync method, as I understand it, it's that if there are dirty pages in the page cache for files on the fuse filesystem, the system will initiate a write-out on them and wait for it to finish. But if the fuse userspace is frozen, the write-out will never complete. Paul. - 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