From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 29172] New: releasing loop on top of other loop leads to deadlock
Date: Fri, 18 Feb 2011 09:16:42 +0100 [thread overview]
Message-ID: <201102180916.42494.arnd@arndb.de> (raw)
In-Reply-To: <20110217131244.bb64711a.akpm@linux-foundation.org>
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
parent reply other threads:[~2011-02-18 8:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110217131244.bb64711a.akpm@linux-foundation.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201102180916.42494.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox