On Wed, 6 Mar 2013 07:59:01 -0800 Mandeep Singh Baines <msb@xxxxxxxxxxxx> wrote: > On Wed, Mar 6, 2013 at 4:06 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > On Wed, 6 Mar 2013 10:09:14 +0100 > > Ingo Molnar <mingo@xxxxxxxxxx> wrote: > > > >> > >> * Mandeep Singh Baines <msb@xxxxxxxxxxxx> wrote: > >> > >> > On Tue, Mar 5, 2013 at 5:16 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > >> > > On Tue, Mar 05, 2013 at 08:05:07PM -0500, J. Bruce Fields wrote: > >> > >> If it's really just a 2-line patch to try_to_freeze(), could it just be > >> > >> carried out-of-tree by people that are specifically working on tracking > >> > >> down these problems? > >> > >> > >> > >> But I don't have strong feelings about it--as long as it doesn't result > >> > >> in the same known issues getting reported again and again.... > >> > > > >> > > Agreed, I don't think a Kconfig option is justified for this. If this > >> > > is really important, annotate broken paths so that it doesn't trigger > >> > > spuriously; otherwise, please just remove it. > >> > > > >> > > >> > Fair enough. Let's revert then. I'll rework to use a lockdep annotation. > >> > > >> > Maybe, add a new lockdep API: > >> > > >> > lockdep_set_held_during_freeze(lock); > >> > > >> > Then when we do the check, ignore any locks that set this bit. > >> > > >> > Ingo, does this seem like a reasonable design to you? > >> > >> Am I reading the discussion correctly that the new warnings show REAL potential > >> deadlock scenarios, which can hit real users and can lock their box up in entirely > >> real usage scenarios? > >> > >> If yes then guys we _really_ don't want to use lockdep annotation to _HIDE_ bugs. > >> We typically use them to teach lockdep about things it does not know about. > >> > >> How about fixing the deadlocks instead? > >> > > > > I do see how the freezer might fail to suspend certain tasks, but I > > don't see the deadlock scenario here in the NFS/RPC case. Can someone > > outline a situation where this might end up deadlocking? If not, then > > I'd be inclined to say that while this may be a problem, the warning is > > excessive... > > > > In general, holding a lock and freezing can cause a deadlock if: > > 1) you froze via the cgroup_freezer subsystem and a task in another > cgroup tried to acquire the same lock > 2) the lock was needed later is suspend/hibernate. For example, if the > lock was needed in dpm_suspend by one of the device callbacks. For > hibernate, you also need to worry about any locks that need to be > acquired in order to write to the swap device. > 3) another freezing task blocked on this lock and held other locks > needed later in suspend. If that task were skipped by the freezer, you > would deadlock > > You will block/prevent suspend if: > > 4) another freezing task blocked on this lock and was unable to freeze > > I think 1) and 4) can happen for the NFS/RPC case. Case 1) requires > cgroup freezer. Case 4) while not causing a deadlock could prevent > your laptop/phone from sleeping and end up burning all your battery. > If suspend is initiated via lid close you won't even know about the > failure. > We're aware of #4. That was the intent of adding try_to_freeze() into this codepath in the first place. It's not a great solution for obvious reasons, but we don't have another at the moment. For #1 I'm not sure what to do. I'm that familiar with cgroups or how the freezer works. The bottom line is that we have a choice -- we can either rip out this new lockdep warning, or rip out the code that causes it to fire. If we rip out the warning we may miss some legit cases where we might possibly have hit a deadlock. If we rip out the code that causes it to fire, then we exacerbate the #4 problem above. That will effectively make it so that you can't suspend the host whenever NFS is doing anything moderately active. Ripping out the warning seems like the best course of action in the near term, but it's not my call... -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
