From: Nikolay Borisov <nborisov@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 06/16] btrfs: move clearing of EXCL_OP out of __cancel_balance
Date: Fri, 20 Apr 2018 10:02:21 +0300 [thread overview]
Message-ID: <c0d64179-0b4a-7964-b75e-deb0b470f829@suse.com> (raw)
In-Reply-To: <c5cb79f4b8f36ce894e9e58903029d3a92722d5c.1524146555.git.dsterba@suse.com>
On 19.04.2018 19:33, David Sterba wrote:
> Make the clearning visible in the callers so we can pair it with the
> test_and_set part.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/ioctl.c | 2 +-
> fs/btrfs/volumes.c | 13 +++++++------
> 2 files changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index b93dea445802..582bde5b7eda 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -4656,7 +4656,7 @@ static long btrfs_ioctl_balance(struct file *file, void __user *arg)
> * Ownership of bctl and filesystem flag BTRFS_FS_EXCL_OP
> * goes to to btrfs_balance. bctl is freed in __cancel_balance,
> * or, if restriper was paused all the way until unmount, in
> - * free_fs_info. The flag is cleared in __cancel_balance.
> + * free_fs_info. The flag should be cleared after __cancel_balance.
> */
> need_unlock = false;
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index e0bd181dc9e0..5c83ebc8e199 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -3760,8 +3760,6 @@ static void __cancel_balance(struct btrfs_fs_info *fs_info)
> ret = del_balance_item(fs_info);
> if (ret)
> btrfs_handle_fs_error(fs_info, ret, NULL);
> -
> - clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
> }
>
> /* Non-zero return value signifies invalidity */
> @@ -3919,6 +3917,7 @@ int btrfs_balance(struct btrfs_balance_control *bctl,
> if ((ret && ret != -ECANCELED && ret != -ENOSPC) ||
> balance_need_close(fs_info)) {
> __cancel_balance(fs_info);
> + clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
> }
>
> wake_up(&fs_info->balance_wait_q);
> @@ -3927,10 +3926,10 @@ int btrfs_balance(struct btrfs_balance_control *bctl,
> out:
> if (bctl->flags & BTRFS_BALANCE_RESUME)
> __cancel_balance(fs_info);
> - else {
> + else
> kfree(bctl);
> - clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
> - }
> + clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
> +
> return ret;
> }
>
> @@ -4089,8 +4088,10 @@ int btrfs_cancel_balance(struct btrfs_fs_info *fs_info)
> mutex_lock(&fs_info->volume_mutex);
> mutex_lock(&fs_info->balance_mutex);
>
> - if (fs_info->balance_ctl)
> + if (fs_info->balance_ctl) {
> __cancel_balance(fs_info);
> + clear_bit(BTRFS_FS_EXCL_OP, &fs_info->flags);
> + }
>
> mutex_unlock(&fs_info->volume_mutex);
> }
>
next prev parent reply other threads:[~2018-04-20 7:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 16:33 [PATCH v2 00/16] Kill fs_info::volume_mutex David Sterba
2018-04-19 16:33 ` [PATCH v2 01/16] btrfs: squeeze btrfs_dev_replace_continue_on_mount to its caller David Sterba
2018-04-19 16:33 ` [PATCH v2 02/16] btrfs: make success path out of btrfs_init_dev_replace_tgtdev more clear David Sterba
2018-04-19 16:33 ` [PATCH v2 03/16] btrfs: export and rename free_device David Sterba
2018-04-19 16:33 ` [PATCH v2 04/16] btrfs: move btrfs_init_dev_replace_tgtdev to dev-replace.c and make static David Sterba
2018-04-19 16:33 ` [PATCH v2 05/16] btrfs: move volume_mutex to callers of btrfs_rm_device David Sterba
2018-04-19 16:33 ` [PATCH v2 06/16] btrfs: move clearing of EXCL_OP out of __cancel_balance David Sterba
2018-04-20 7:02 ` Nikolay Borisov [this message]
2018-04-20 7:35 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 07/16] btrfs: add proper safety check before resuming dev-replace David Sterba
2018-04-20 7:04 ` Nikolay Borisov
2018-04-20 7:36 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 08/16] btrfs: add sanity check when resuming balance after mount David Sterba
2018-04-20 7:38 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 09/16] btrfs: cleanup helpers that reset balance state David Sterba
2018-04-20 7:07 ` Nikolay Borisov
2018-04-20 11:28 ` David Sterba
2018-04-20 9:04 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 10/16] btrfs: remove wrong use of volume_mutex from btrfs_dev_replace_start David Sterba
2018-04-19 16:33 ` [PATCH v2 11/16] btrfs: kill btrfs_fs_info::volume_mutex David Sterba
2018-04-19 16:33 ` [PATCH v2 12/16] btrfs: track running balance in a simpler way David Sterba
2018-04-20 7:52 ` Anand Jain
2018-04-20 11:58 ` David Sterba
2018-04-20 12:19 ` David Sterba
2018-04-20 13:32 ` Anand Jain
2018-04-27 2:10 ` Anand Jain
2018-04-27 16:10 ` David Sterba
2018-04-19 16:33 ` [PATCH v2 13/16] btrfs: move and comment read-only check in btrfs_cancel_balance David Sterba
2018-04-20 9:13 ` Anand Jain
2018-04-20 11:59 ` David Sterba
2018-04-20 12:06 ` [PATCH v2.1 " David Sterba
2018-04-27 2:02 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 14/16] btrfs: drop lock parameter from update_ioctl_balance_args and rename David Sterba
2018-04-20 9:21 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 15/16] btrfs: use mutex in btrfs_resume_balance_async David Sterba
2018-04-20 9:25 ` Anand Jain
2018-04-19 16:33 ` [PATCH v2 16/16] btrfs: open code set_balance_control 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=c0d64179-0b4a-7964-b75e-deb0b470f829@suse.com \
--to=nborisov@suse.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