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: Fri, 06 Jul 2007 09:13:27 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: nigel@...pend2.net CC: rjw@...k.pl, pavel@....cz, linux-pm@...ts.linux-foundation.org, nigel@...pend2.net, benh@...nel.crashing.org, linux-kernel@...r.kernel.org, mjg59@...f.ucam.org, oliver@...kum.org, paulus@...ba.org, miklos@...redi.hu, mingo@...e.hu Subject: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer > To get more serious and practical though, I think the solution is to > fuzz the userspace/kernelspace distinction. What we really want to > do is freeze things that submit I/O, then sync, then freeze anything > that processes I/O and needs to be frozen. In effect, redefine fuse > processes as freezeable kernel threads. Another myth, that has been debunked already. The problem is: how do you define fuse processes? There's no theoretical or even practial way to do that. Miklos - 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