Hi!
> > > The problem with FUSE is related to the fact that the freezer can't
> > > freeze uninterruptible tasks and we said that perhaps we might avoid
> > > it if FUSE was made freezing-aware. Still, no one has gone in this
> > > direction and I don't know of any plans to do that.
> >
> > I thought we have fully explored this direction. Lots of emails, and
> > an IRC session with Pavel. Conclusion:
>
> 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
The list of neccessary PIDs is not known to the kernel. FUSE servers
may depend on another parts of userland.
--
(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 [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]
