From: Josef Bacik <josef@redhat.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux BTRFS <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@redhat.com>
Subject: Re: [2.6.38-rc1] btrfs potential false-positive lockdep report...
Date: Thu, 20 Jan 2011 11:08:49 -0500 [thread overview]
Message-ID: <20110120160849.GA6609@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <AANLkTinTkAtUkZApi-EMpTx-R7sBagLnd4uYnUTL5Lek@mail.gmail.com>
On Thu, Jan 20, 2011 at 10:53:51AM +0700, Daniel J Blueman wrote:
> I saw a lockdep report with an instrumented 2.6.38-rc1 kernel [1].
>
> Checking the code, it looks more likely a false-positive due to the
> lock manipulation to satisfy lockdep, since CONFIG_DEBUG_LOCK_ALLOC is
> defined.
>
> Is this the case?
>
Yeah these pop up every once and a while, its safe to just ignore it. Thanks,
Josef
prev parent reply other threads:[~2011-01-20 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 3:53 [2.6.38-rc1] btrfs potential false-positive lockdep report Daniel J Blueman
2011-01-20 16:08 ` Josef Bacik [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=20110120160849.GA6609@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).