From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] More lockdep annotations
Date: Fri, 7 Jun 2019 15:31:12 +0200 [thread overview]
Message-ID: <20190607133112.GC30187@twin.jikos.cz> (raw)
In-Reply-To: <384c555b-3e7b-2c38-0204-8cf827386915@suse.com>
On Wed, Jun 05, 2019 at 10:34:24AM +0300, Nikolay Borisov wrote:
>
>
> On 31.05.19 г. 20:01 ч., David Sterba wrote:
> > Lockdep annotations are better than comments about necessary locks.
> >
> > David Sterba (5):
> > btrfs: tests: add locks around add_extent_mapping
> > btrfs: assert extent map tree lock in add_extent_mapping
> > btrfs: assert tree mod log lock in __tree_mod_log_insert
> > btrfs: assert delayed ref lock in btrfs_find_delayed_ref_head
> > btrfs: assert bio list lock in merge_rbio
> >
> > fs/btrfs/ctree.c | 4 ++--
> > fs/btrfs/delayed-ref.c | 7 ++++---
> > fs/btrfs/extent_map.c | 2 ++
> > fs/btrfs/raid56.c | 4 ++--
> > fs/btrfs/tests/extent-map-tests.c | 22 ++++++++++++++++++++++
> > 5 files changed, 32 insertions(+), 7 deletions(-)
> >
>
>
> For the whole series :
>
> Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Thanks, series moved to misc-next.
prev parent reply other threads:[~2019-06-07 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 17:01 [PATCH 0/5] More lockdep annotations David Sterba
2019-05-31 17:01 ` [PATCH 1/5] btrfs: tests: add locks around add_extent_mapping David Sterba
2019-05-31 17:01 ` [PATCH 2/5] btrfs: assert extent map tree lock in add_extent_mapping David Sterba
2019-05-31 17:01 ` [PATCH 3/5] btrfs: assert tree mod log lock in __tree_mod_log_insert David Sterba
2019-05-31 17:01 ` [PATCH 4/5] btrfs: assert delayed ref lock in btrfs_find_delayed_ref_head David Sterba
2019-05-31 17:01 ` [PATCH 5/5] btrfs: assert bio list lock in merge_rbio David Sterba
2019-06-05 7:34 ` [PATCH 0/5] More lockdep annotations Nikolay Borisov
2019-06-07 13:31 ` David Sterba [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=20190607133112.GC30187@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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