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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
