From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/6] Btrfs lockdep and locking cleanups
Date: Tue, 27 Mar 2018 20:48:20 +0200 [thread overview]
Message-ID: <cover.1522176187.git.dsterba@suse.com> (raw)
A few cleanups related to lockdep and locking. The btrfs_show_devname is
a functional change, uses the same mechanism as btrfs_ioctl_dev_info or
btrfs_ioctl_fs_info so that's not a new thing.
David Sterba (6):
btrfs: use lockdep_assert_held for spinlocks
btrfs: use lockdep_assert_held for mutexes
btrfs: update barrier in should_cow_block
btrfs: use RCU in btrfs_show_devname for device list traversal
btrfs: remove stale comments about fs_mutex
btrfs: split dev-replace locking helpers for read and write
fs/btrfs/acl.c | 8 -----
fs/btrfs/ctree.c | 4 +--
fs/btrfs/delayed-ref.c | 6 ++--
fs/btrfs/dev-replace.c | 98 +++++++++++++++++++++++++-------------------------
fs/btrfs/dev-replace.h | 6 ++--
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/qgroup.c | 2 +-
fs/btrfs/reada.c | 10 +++---
fs/btrfs/scrub.c | 18 +++++-----
fs/btrfs/super.c | 15 +++++---
fs/btrfs/volumes.c | 28 +++++++--------
11 files changed, 98 insertions(+), 99 deletions(-)
--
2.16.2
next reply other threads:[~2018-03-27 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:48 David Sterba [this message]
2018-03-27 18:48 ` [PATCH 1/6] btrfs: use lockdep_assert_held for spinlocks David Sterba
2018-03-27 18:48 ` [PATCH 2/6] btrfs: use lockdep_assert_held for mutexes David Sterba
2018-03-27 18:48 ` [PATCH 3/6] btrfs: update barrier in should_cow_block David Sterba
2018-03-27 18:48 ` [PATCH 4/6] btrfs: use RCU in btrfs_show_devname for device list traversal David Sterba
2018-03-27 20:09 ` Anand Jain
2018-03-27 18:48 ` [PATCH 5/6] btrfs: remove stale comments about fs_mutex David Sterba
2018-03-27 18:48 ` [PATCH 6/6] btrfs: split dev-replace locking helpers for read and write David Sterba
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=cover.1522176187.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@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.