From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6.23.1] possible circular locking dependency detected
Date: Sun, 14 Oct 2007 01:59:44 +0200 [thread overview]
Message-ID: <1192319984.5625.21.camel@lappy> (raw)
In-Reply-To: <1192317596.5625.12.camel@lappy>
On Sun, 2007-10-14 at 01:19 +0200, Peter Zijlstra wrote:
> On Sun, 2007-10-14 at 00:36 +0200, Folkert van Heusden wrote:
> > I've got a deja-vu feeling for this one but in any case:
> >
> I seems that patch hasn't made it into .23... I'll stick it in the
> lockdep tree aimed at .24.
Could you try:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git v2.6.24-lockdep
on top of current -linus, I just pushed out the patch that should fix it:
lockdep: per filesystem inode lock class
(still hasn't replicated though, so might take a while)
prev parent reply other threads:[~2007-10-13 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 22:36 [2.6.23.1] possible circular locking dependency detected Folkert van Heusden
2007-10-13 23:19 ` Peter Zijlstra
2007-10-13 23:59 ` Peter Zijlstra [this message]
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=1192319984.5625.21.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
/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