From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 3/6] btrfs: update device_list_mutex protected items
Date: Wed, 30 May 2018 14:58:18 +0800 [thread overview]
Message-ID: <20180530065821.28385-4-anand.jain@oracle.com> (raw)
In-Reply-To: <20180530065821.28385-1-anand.jain@oracle.com>
Include items of fs_uuids::fs_devices to be protected by
device_list_mutex, like (but not limited to) fs_devices::opened,
fs_devices::total_devices and fs_devices::num_devices. This is
been done in the code already.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
fs/btrfs/volumes.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 0fdb9b717398..e3dd25238eb9 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -164,7 +164,8 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
*
* fs_devices::device_list_mutex (per-fs, with RCU)
* ------------------------------------------------
- * protects updates to fs_devices::devices, ie. adding and deleting
+ * Protects updates to fs_uuids::fs_devices items, and fs_devices::devices, ie.
+ * adding and deleting.
*
* simple list traversal with read-only actions can be done with RCU protection
*
--
2.7.0
next prev parent reply other threads:[~2018-05-30 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 6:58 [PATCH 0/6] fix device_list_mutex usage and cleanups in device_list_add() Anand Jain
2018-05-30 6:58 ` [PATCH 1/6] btrfs: do btrfs_free_stale_devices() outside of device_list_add() Anand Jain
2018-05-30 6:58 ` [PATCH 2/6] btrfs: fix device_list_add() missing device_list_mutex() Anand Jain
2018-05-30 6:58 ` Anand Jain [this message]
2018-05-30 6:58 ` [PATCH 4/6] btrfs: btrfs_free_stale_devices() rename local variables Anand Jain
2018-05-30 6:58 ` [PATCH 5/6] btrfs: fix btrfs_free_stale_devices() with needed locks Anand Jain
2018-05-30 6:58 ` [PATCH 6/6] btrfs: rename btrfs_free_stale_devices drop btrfs prefix Anand Jain
2018-05-30 7:11 ` Nikolay Borisov
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=20180530065821.28385-4-anand.jain@oracle.com \
--to=anand.jain@oracle.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 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).