> The problem is not with fuse. The problem is generic in nature. > > If you remove the freezer, user space remains active until the last CPU > goes into suspend. It can do syscalls. Or do you know a clean way to exempt > only the tasks fuse might use? > > Now device drivers have a guaranteed temporal sequence: > > last io -> suspend() -> resume() [or disconnect()] -> new io No, that's always been bullshit. You can have IOs emitted by kernel threads (think knfsd, and that's just one among many others). Beside, relying on having userland frozen means that your driver will be unable to be "live" suspended/resumed for more ambitious dynamic power management schemes. So it's always been wrong, imho, to rely on that. I've had powermac STR work fine without the freezer for years, and few drivers have been a problem, and we just fixed them. The freezer thingy, at best, hides problems, causing them not to be fixed. > This is because suspend() is called after the freezer goes into action. If > you remove the freezer, you need to deal with > > 1. io to suspended devices > 2. resume() assuming that the device is in the state suspend() left it > 3. io changing a device's state while suspend is saving it > > and you need to fix this for all device drivers, not just those fuse is > involved with. Removing the freezer means doing a more or less full > audit of every driver and additional locking in many drivers. Yes, more or less. The good news is that a whole lot of drivers don't really care much, and in some cases, things can be done trivially with a bit of help from the upper layers. But yeah, as I've been explaining over and over again, the lazy approach here doesn't work. Ben. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
