Hello, Trond. On Thu, Jan 03, 2013 at 10:12:32PM +0000, Myklebust, Trond wrote: > > The analysis is likely completely wrong, so please don't go off doing > > something unnecessary. Please take look at what's causing the > > deadlocks again. > > The analysis is a no-brainer: > We see a deadlock due to one work item waiting for completion of another > work item that is queued on the same CPU. There is no other dependency > between the two work items. What do you mean "waiting for completion of"? Is one flushing the other? Or is one waiting for the other to take certain action? How are the two work items related? Are they queued on the same workqueue? Can you create a minimal repro case of the observed deadlock? Thanks. -- tejun -- 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
