From: Chris Mason <chris.mason@oracle.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29-rc4: possible circular locking dependency at btrfs_try_spin_lock
Date: Mon, 09 Feb 2009 09:47:00 -0500 [thread overview]
Message-ID: <1234190820.1262.0.camel@think.oraclecorp.com> (raw)
In-Reply-To: <a4423d670902090443v2c0da60g9c8ac4792586b044@mail.gmail.com>
On Mon, 2009-02-09 at 15:43 +0300, Alexander Beregalov wrote:
> Hi
> Is it false positive lockdep warning?
>
Interesting, lockdep must be smarter in linux-next. It's a false
positive, I'll try to fix it up.
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29-rc4: possible circular locking dependency at btrfs_try_spin_lock
Date: Mon, 09 Feb 2009 09:47:00 -0500 [thread overview]
Message-ID: <1234190820.1262.0.camel@think.oraclecorp.com> (raw)
In-Reply-To: <a4423d670902090443v2c0da60g9c8ac4792586b044@mail.gmail.com>
On Mon, 2009-02-09 at 15:43 +0300, Alexander Beregalov wrote:
> Hi
> Is it false positive lockdep warning?
>
Interesting, lockdep must be smarter in linux-next. It's a false
positive, I'll try to fix it up.
-chris
next prev parent reply other threads:[~2009-02-09 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 12:43 2.6.29-rc4: possible circular locking dependency at btrfs_try_spin_lock Alexander Beregalov
2009-02-09 12:43 ` Alexander Beregalov
2009-02-09 13:48 ` Alexander Beregalov
2009-02-09 13:48 ` Alexander Beregalov
2009-02-09 14:47 ` Chris Mason [this message]
2009-02-09 14:47 ` Chris Mason
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=1234190820.1262.0.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.