From: Christian Borntraeger <borntraeger@de.ibm.com>
To: fdmanana@gmail.com
Cc: Chris Mason <clm@fb.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] btrfs lockdep annotation
Date: Tue, 24 Jan 2017 12:27:14 +0100 [thread overview]
Message-ID: <73669801-4a2e-485e-1251-da8723666e22@de.ibm.com> (raw)
In-Reply-To: <CAL3q7H4Y08K4fgBe3k3r_P+YikN_z=3H1H+T6zMYJ+pAS99wzw@mail.gmail.com>
On 01/24/2017 11:22 AM, Filipe Manana wrote:
> On Tue, Jan 24, 2017 at 9:01 AM, Christian Borntraeger
> <borntraeger@de.ibm.com> wrote:
>> Chris,
>>
>> since my bug report about this did not result in any fix and since
>
> It was fixed and the fix landed in 4.10-rc4:
Thanks, I missed that last pull.
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=781feef7e6befafd4d9787d1f7ada1f9ccd504e4
>
>> this disables lockdep before the the code that I want to debug runs
>> here is my attempt to fix it.
>> Please double check if the subclass looks right. It seems to work
>> for me but I do not know enough about btrfs to decide if this is
>> right or not.
>>
>> Christian Borntraeger ():
>> btrfs: add lockdep annotation for btrfs_log_inode
>>
>> fs/btrfs/tree-log.c | 2 +-
>>
>> --
>> 2.7.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2017-01-24 11:27 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
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 [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=73669801-4a2e-485e-1251-da8723666e22@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=clm@fb.com \
--cc=fdmanana@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
all inboxes | Powered by JetHome®