New: releasing loop on top of other loop leads to deadlock
A message that is not in the archive (sent off-list or not yet received): [email protected]/
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Andrew Morton
Quoted 1 line · On Tue, 15 Feb 2011 10:00:57 GMT [email protected] wrote:
post-2.6.37 deadlock in loop. I'd agree with the reporter that Arnd might be involved ;)
Yes, sounds right, we should fix it and get the fix into stable.
This comes from an automated conversion that was done under the assumption that it cannot break from making the locking stricter. A related bug happened in the nbd driver, and I think the solution here should also be to remove the new mutex. Upon closer review of the code, I cannot see any reason why it would actually be needed: there is no global data to be protected and all device specific data is protected by another mutex.
Arnd