From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 05/16] btrfs: move volume_mutex to callers of btrfs_rm_device
Date: Tue, 3 Apr 2018 20:34:12 +0200 [thread overview]
Message-ID: <004920f0f641ebffa974129fe8f4b0d6a9ee9f34.1522780026.git.dsterba@suse.com> (raw)
In-Reply-To: <cover.1522780026.git.dsterba@suse.com>
Move locking and unlocking next to the BTRFS_FS_EXCL_OP bit manipulation
so it's obvious that the two happen at the same time.
Signed-off-by: David Sterba <dsterba@suse.com>
---
fs/btrfs/ioctl.c | 4 ++++
fs/btrfs/volumes.c | 2 --
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index ac85e07f567b..b93dea445802 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -2674,6 +2674,7 @@ static long btrfs_ioctl_rm_dev_v2(struct file *file, void __user *arg)
ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
goto out;
}
+ mutex_lock(&fs_info->volume_mutex);
if (vol_args->flags & BTRFS_DEVICE_SPEC_BY_ID) {
ret = btrfs_rm_device(fs_info, NULL, vol_args->devid);
@@ -2681,6 +2682,7 @@ static long btrfs_ioctl_rm_dev_v2(struct file *file, void __user *arg)
vol_args->name[BTRFS_SUBVOL_NAME_MAX] = '\0';
ret = btrfs_rm_device(fs_info, vol_args->name, 0);
}
+ mutex_unlock(&fs_info->volume_mutex);
clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
if (!ret) {
@@ -2716,6 +2718,7 @@ static long btrfs_ioctl_rm_dev(struct file *file, void __user *arg)
ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
goto out_drop_write;
}
+ mutex_lock(&fs_info->volume_mutex);
vol_args = memdup_user(arg, sizeof(*vol_args));
if (IS_ERR(vol_args)) {
@@ -2730,6 +2733,7 @@ static long btrfs_ioctl_rm_dev(struct file *file, void __user *arg)
btrfs_info(fs_info, "disk deleted %s", vol_args->name);
kfree(vol_args);
out:
+ mutex_unlock(&fs_info->volume_mutex);
clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
out_drop_write:
mnt_drop_write_file(file);
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index df2d6d06e014..e0bd181dc9e0 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -1932,7 +1932,6 @@ int btrfs_rm_device(struct btrfs_fs_info *fs_info, const char *device_path,
u64 num_devices;
int ret = 0;
- mutex_lock(&fs_info->volume_mutex);
mutex_lock(&uuid_mutex);
num_devices = fs_info->fs_devices->num_devices;
@@ -2048,7 +2047,6 @@ int btrfs_rm_device(struct btrfs_fs_info *fs_info, const char *device_path,
out:
mutex_unlock(&uuid_mutex);
- mutex_unlock(&fs_info->volume_mutex);
return ret;
error_undo:
--
2.16.2
next prev parent reply other threads:[~2018-04-03 18:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 18:34 [PATCH 00/16 v1] Kill fs_info::volume_mutex David Sterba
2018-04-03 18:34 ` [PATCH 01/16] btrfs: squeeze btrfs_dev_replace_continue_on_mount to its caller David Sterba
2018-04-05 9:40 ` Anand Jain
2018-04-03 18:34 ` [PATCH 02/16] btrfs: make success path out of btrfs_init_dev_replace_tgtdev more clear David Sterba
2018-04-05 9:40 ` Anand Jain
2018-04-03 18:34 ` [PATCH 03/16] btrfs: export and rename free_device David Sterba
2018-04-05 9:41 ` Anand Jain
2018-04-03 18:34 ` [PATCH 04/16] btrfs: move btrfs_init_dev_replace_tgtdev to dev-replace.c and make static David Sterba
2018-04-05 9:41 ` Anand Jain
2018-04-03 18:34 ` David Sterba [this message]
2018-04-05 9:41 ` [PATCH 05/16] btrfs: move volume_mutex to callers of btrfs_rm_device Anand Jain
2018-04-05 14:28 ` David Sterba
2018-04-03 18:34 ` [PATCH 06/16] btrfs: move clearing of EXCL_OP out of __cancel_balance David Sterba
2018-04-05 9:42 ` Anand Jain
2018-04-05 14:04 ` David Sterba
2018-04-03 18:34 ` [PATCH 07/16] btrfs: add proper safety check before resuming dev-replace David Sterba
2018-04-06 20:06 ` Sasha Levin
2018-04-07 6:42 ` Anand Jain
2018-04-07 10:43 ` Anand Jain
2018-04-09 11:43 ` David Sterba
2018-04-03 18:34 ` [PATCH 08/16] btrfs: add sanity check when resuming balance after mount David Sterba
2018-04-06 20:06 ` Sasha Levin
2018-04-09 7:23 ` Anand Jain
2018-04-16 6:10 ` Anand Jain
2018-04-17 17:38 ` David Sterba
2018-04-03 18:34 ` [PATCH 09/16] btrfs: cleanup helpers that reset balance state David Sterba
2018-04-09 7:43 ` Anand Jain
2018-04-03 18:34 ` [PATCH 10/16] btrfs: remove wrong use of volume_mutex from btrfs_dev_replace_start David Sterba
2018-04-09 8:39 ` Anand Jain
2018-04-09 8:54 ` Nikolay Borisov
2018-04-09 9:31 ` Anand Jain
2018-04-09 11:53 ` David Sterba
2018-04-09 14:44 ` Anand Jain
2018-04-09 14:55 ` Anand Jain
2018-04-03 18:34 ` [PATCH 11/16] btrfs: kill btrfs_fs_info::volume_mutex David Sterba
2018-04-09 14:52 ` Anand Jain
2018-04-13 5:30 ` Anand Jain
2018-04-13 13:15 ` David Sterba
2018-04-03 18:34 ` [PATCH 12/16] btrfs: track running balance in a simpler way David Sterba
2018-04-03 18:34 ` [PATCH 13/16] btrfs: remove redundant read-only check from btrfs_cancel_balance David Sterba
2018-04-16 9:43 ` Anand Jain
2018-04-17 17:47 ` David Sterba
2018-04-03 18:34 ` [PATCH 14/16] btrfs: drop lock parameter from update_ioctl_balance_args and rename David Sterba
2018-04-03 18:34 ` [PATCH 15/16] btrfs: use mutex in btrfs_resume_balance_async David Sterba
2018-04-03 18:34 ` [PATCH 16/16] btrfs: open code set_balance_control David Sterba
2018-04-09 15:24 ` Anand Jain
2018-04-05 14:31 ` [PATCH 00/16 v1] Kill fs_info::volume_mutex 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=004920f0f641ebffa974129fe8f4b0d6a9ee9f34.1522780026.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 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).