linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH] btrfs: ioctl: reorder exclusive op check in RM_DEV
Date: Wed, 4 May 2016 10:51:11 +0100	[thread overview]
Message-ID: <CAL3q7H4X5NjNFGRp8oj87pkHkZxPMvicM7=Kh0r-MCkO7Y__yA@mail.gmail.com> (raw)
In-Reply-To: <1462354346-17654-1-git-send-email-dsterba@suse.com>

On Wed, May 4, 2016 at 10:32 AM, David Sterba <dsterba@suse.com> wrote:
> From: David Sterba <dsterba@suse.cz>
>
> Move the op exclusivity check before the other code (same as in
> ADD_DEV).
>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  fs/btrfs/ioctl.c | 23 +++++++++++------------
>  1 file changed, 11 insertions(+), 12 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index e3239272fa61..45beb6dd8417 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -2680,32 +2680,31 @@ static long btrfs_ioctl_rm_dev(struct file *file, void __user *arg)
>         if (ret)
>                 return ret;
>
> +       if (atomic_xchg(&root->fs_info->mutually_exclusive_operation_running,
> +                       1)) {
> +               ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> +               goto out_drop_write;
> +       }
> +
>         vol_args = memdup_user(arg, sizeof(*vol_args));
>         if (IS_ERR(vol_args)) {
>                 ret = PTR_ERR(vol_args);
> -               goto err_drop;
> +               goto out_drop_write;

goto out, otherwise
root->fs_info->mutually_exclusive_operation_running remains with value
1 forever...

>         }
>
>         vol_args->name[BTRFS_PATH_NAME_MAX] = '\0';
> -
> -       if (atomic_xchg(&root->fs_info->mutually_exclusive_operation_running,
> -                       1)) {
> -               ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> -               goto out;
> -       }
> -
>         mutex_lock(&root->fs_info->volume_mutex);
>         ret = btrfs_rm_device(root, vol_args->name);
>         mutex_unlock(&root->fs_info->volume_mutex);
> -       atomic_set(&root->fs_info->mutually_exclusive_operation_running, 0);
>
>         if (!ret)
>                 btrfs_info(root->fs_info, "disk deleted %s",vol_args->name);
> -
> -out:
>         kfree(vol_args);
> -err_drop:
> +out:
> +       atomic_set(&root->fs_info->mutually_exclusive_operation_running, 0);
> +out_drop_write:
>         mnt_drop_write_file(file);
> +
>         return ret;
>  }
>
> --
> 2.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

  reply	other threads:[~2016-05-04  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04  9:32 [PATCH] btrfs: ioctl: reorder exclusive op check in RM_DEV David Sterba
2016-05-04  9:51 ` Filipe Manana [this message]
2016-05-04 12:10 ` [PATCH v2] " 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='CAL3q7H4X5NjNFGRp8oj87pkHkZxPMvicM7=Kh0r-MCkO7Y__yA@mail.gmail.com' \
    --to=fdmanana@gmail.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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).