From: Chris Mason <clm@fb.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: btrfs: still lockdep splat for 4.9-rc5+ (btrfs_log_inode)
Date: Sat, 26 Nov 2016 08:46:38 -0500 [thread overview]
Message-ID: <20161126134638.GA79987@clm-mbp.masoncoding.com> (raw)
In-Reply-To: <b9063be2-8c01-2c15-ca2d-8460594128cf@de.ibm.com>
On Fri, Nov 25, 2016 at 10:03:25AM +0100, Christian Borntraeger wrote:
>FWIW, I still see the lockdep splat in btrfs in 4.9-rc5+
Filipe reworked the code to avoid taking the same lock twice. As far as
I can tell, this just needs some annotation.
-chris
next prev parent reply other threads:[~2016-11-26 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 9:03 btrfs: still lockdep splat for 4.9-rc5+ (btrfs_log_inode) Christian Borntraeger
2016-11-26 13:46 ` Chris Mason [this message]
2016-11-28 20:12 ` Liu Bo
2017-01-24 9:01 ` [PATCH 0/1] btrfs lockdep annotation Christian Borntraeger
2017-01-24 9:01 ` [PATCH 2/2] btrfs: add lockdep annotation for btrfs_log_inode Christian Borntraeger
2017-01-24 10:22 ` [PATCH 0/1] btrfs lockdep annotation Filipe Manana
2017-01-24 11:27 ` Christian Borntraeger
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=20161126134638.GA79987@clm-mbp.masoncoding.com \
--to=clm@fb.com \
--cc=borntraeger@de.ibm.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).