* Re: [Bugme-new] [Bug 29172] New: releasing loop on top of other loop leads to deadlock
[not found] ` <20110217131244.bb64711a.akpm@linux-foundation.org>
@ 2011-02-18 8:16 ` Arnd Bergmann
0 siblings, 0 replies; only message in thread
From: Arnd Bergmann @ 2011-02-18 8:16 UTC (permalink / raw)
To: Andrew Morton; +Cc: Rafael J. Wysocki, Maciej Rutecki, linux-kernel
On Thursday 17 February 2011, Andrew Morton wrote:
> On Tue, 15 Feb 2011 10:00:57 GMT
> bugzilla-daemon@bugzilla.kernel.org 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
^ permalink raw reply [flat|nested] only message in thread