> 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
