Re: Getting rid of freezer for suspend [was Re: [fuse-devel][PATCH] fuse: make fuse daemon frozen along with kernel threads]
From: Pavel Machek
Date: Tue Feb 12 2013 - 05:46:19 EST
> > That's potentially deeadlock-prone, because a task waiting for mutex X may
> > very well be holding mutex Y, so if there's another task waiting for mutex Y,
> > it needs to be frozen at the same time.
> >> The only little detail is how do we implement that...
> > This means the only way I can see would be to hack the mutex code so that the
> > try_to_freeze() was called for user space tasks after the
> > sched_preempt_enable_no_resched() before schedule().
> > That shouldn't be a big deal performance-wise, because we are in the slow
> > path anyway then. I'm not sure if Peter Z will like it, though.
> > Moreover, a task waiting for a mutex may be holding a semaphore or be
> > participating in some other mutual-exclusion mechanism, so we'd need to
> > address them all. Plus, as noted by Pavel, freezing those things would make
> > it difficult to save hibernation images to us.
> Well, as a first step I could cook up a patch that adds a flag to the
> mutex indicating that it's freezable. Fuse would mark its mutexes
> (and the mutexes that VFS uses on its behalf) as freezable. That way
> we don't interfere with hibernation, except if hibernation uses fuse
> but that's a very special case.
Yes please. If that is doable, that's the right solution.
(After all, with FUSE, filesystem clients are just doing IPC. In ideal
world, that would be freezeable and killable with -9).
(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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/