> 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 _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
