From: Su Yue <l@damenly.su>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH RFC 2/3] btrfs: consolidate device_list_mutex in prepare_sprout to its parent
Date: Fri, 20 Aug 2021 15:51:03 +0800 [thread overview]
Message-ID: <y28weeg4.fsf@damenly.su> (raw)
In-Reply-To: <8b8e72c87d0ee97da1b2e243a24b68d84d0ac3b9.1629396187.git.anand.jain@oracle.com>
On Fri 20 Aug 2021 at 02:18, Anand Jain <anand.jain@oracle.com>
wrote:
> btrfs_prepare_sprout() moves seed devices into its own struct
> fs_devices,
> so that its parent function btrfs_init_new_device() can add the
> new sprout
> device to fs_info->fs_devices.
>
> Both btrfs_prepare_sprout() and btrfs_init_new_device() needs
> device_list_mutex. But they are holding it sequentially, thus
> creates a
> small window to an opportunity to race. Close this opportunity
> and hold
> device_list_mutex common to both btrfs_init_new_device() and
> btrfs_prepare_sprout().
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> RFC because I haven't identified the other thread which could
> race with
> this, but still does this cleanup makes sense?
>
> fs/btrfs/volumes.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 91b8422b3f67..f490d1897c56 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -2366,6 +2366,8 @@ static int btrfs_prepare_sprout(struct
> btrfs_fs_info *fs_info)
> u64 super_flags;
>
> lockdep_assert_held(&uuid_mutex);
> + lockdep_assert_held(&fs_devices->device_list_mutex);
> +
>
Just a reminder: clone_fs_devices() still takes the mutex in
misc-next.
> if (!fs_devices->seeding)
> return -EINVAL;
>
> @@ -2397,7 +2399,6 @@ static int btrfs_prepare_sprout(struct
> btrfs_fs_info *fs_info)
> INIT_LIST_HEAD(&seed_devices->alloc_list);
> mutex_init(&seed_devices->device_list_mutex);
>
> - mutex_lock(&fs_devices->device_list_mutex);
> list_splice_init_rcu(&fs_devices->devices,
> &seed_devices->devices,
> synchronize_rcu);
> list_for_each_entry(device, &seed_devices->devices, dev_list)
> @@ -2413,7 +2414,6 @@ static int btrfs_prepare_sprout(struct
> btrfs_fs_info *fs_info)
> generate_random_uuid(fs_devices->fsid);
> memcpy(fs_devices->metadata_uuid, fs_devices->fsid,
> BTRFS_FSID_SIZE);
> memcpy(disk_super->fsid, fs_devices->fsid, BTRFS_FSID_SIZE);
> - mutex_unlock(&fs_devices->device_list_mutex);
>
> super_flags = btrfs_super_flags(disk_super) &
> ~BTRFS_SUPER_FLAG_SEEDING;
> @@ -2588,6 +2588,7 @@ int btrfs_init_new_device(struct
> btrfs_fs_info *fs_info, const char *device_path
> device->dev_stats_valid = 1;
> set_blocksize(device->bdev, BTRFS_BDEV_BLOCKSIZE);
>
> + mutex_lock(&fs_devices->device_list_mutex);
> if (seeding_dev) {
> btrfs_clear_sb_rdonly(sb);
> ret = btrfs_prepare_sprout(fs_info);
>
the erorr case:
if (ret) {
mutex_unlock(&fs_devices->device_list_mutex);
...
}
Thanks.
--
Su
> @@ -2599,7 +2600,6 @@ int btrfs_init_new_device(struct
> btrfs_fs_info *fs_info, const char *device_path
>
> device->fs_devices = fs_devices;
>
> - mutex_lock(&fs_devices->device_list_mutex);
> mutex_lock(&fs_info->chunk_mutex);
> list_add_rcu(&device->dev_list, &fs_devices->devices);
> list_add(&device->dev_alloc_list, &fs_devices->alloc_list);
next prev parent reply other threads:[~2021-08-20 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:18 [PATCH 0/3] btrf_show_devname related fixes Anand Jain
2021-08-19 18:18 ` [PATCH 1/3] btrfs: fix comment about the btrfs_show_devname Anand Jain
2021-08-19 18:18 ` [PATCH RFC 2/3] btrfs: consolidate device_list_mutex in prepare_sprout to its parent Anand Jain
2021-08-20 7:51 ` Su Yue [this message]
2021-08-20 8:53 ` Anand Jain
2021-08-21 14:57 ` Su Yue
2021-08-21 15:00 ` Su Yue
2021-08-23 10:34 ` Anand Jain
2021-08-23 10:54 ` Anand Jain
2021-08-23 12:20 ` David Sterba
2021-08-19 18:18 ` [PATCH RFC 3/3] btrfs: use latest_bdev in btrfs_show_devname Anand Jain
2021-08-20 7:31 ` Su Yue
2021-08-20 9:13 ` Anand Jain
2021-08-20 10:57 ` David Sterba
2021-08-20 11:03 ` Anand Jain
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=y28weeg4.fsf@damenly.su \
--to=l@damenly.su \
--cc=anand.jain@oracle.com \
--cc=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 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).