Re: [Bugme-new] [Bug 29172] New: releasing loop on top of other loop leads to deadlock

[Arnd Bergmann]

On Thursday 17 February 2011, Andrew Morton wrote:
> On Tue, 15 Feb 2011 10:00:57 GMT
> bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=29172
> 
> 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
--
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/