| 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: <Pine.LNX.4.44L0.0707210954490.8201-100000@netrider.rowland.org> Date: Sat, 21 Jul 2007 09:56:27 -0400 (EDT) From: Alan Stern <stern@...land.harvard.edu> To: Nigel Cunningham <nigel@...el.suspend2.net> cc: Miklos Szeredi <miklos@...redi.hu>, <rjw@...k.pl>, <miltonm@....com>, <ying.huang@...el.com>, <linux-kernel@...r.kernel.org>, <david@...g.hm>, <linux-pm@...ts.linux-foundation.org>, <jbms@....edu> Subject: Re: [linux-pm] Re: Hibernation considerations On Sat, 21 Jul 2007, Nigel Cunningham wrote: > What am I missing in the following suggested solution? > > 1) In the freezer code, we implement a new TIF_LATEFREEZE process flag, which, > when set, causes a userspace process to be frozen with kernel threads > instead of with userspace ones. When freezing, we freezing !TIF_LATEFREEZE, > sync and then freeze TIF_LATEFREEZE and freezable kernel threads. > > 2) In the fuse code, the PID of the process that will do the work gets passed > to the fuse kernel code when the mount is done. The kernel code sets the > TIF_LATEFREEZE flag, and resets it on umount. What happens when one FUSE filesystem makes use of another? You'll still end up with unfreezable processes, except that now you won't detect them until the LATEFREEZE stage. Alan Stern - 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