> 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/
- Follow-Ups:
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- From: Nigel Cunningham <[email protected]>
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- References:
- [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- From: Pavel Machek <[email protected]>
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- From: Nigel Cunningham <[email protected]>
- [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM
- Prev by Date: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Next by Date: Re: [ANNOUNCE] util-linux-ng 2.13-rc1
- Previous by thread: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- Next by thread: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
- Index(es):
 |