From: Josef Bacik <jbacik@fusionio.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: return btrfs error code for dev excl ops err
Date: Tue, 20 Aug 2013 14:34:05 -0400 [thread overview]
Message-ID: <20130820183405.GH3990@localhost.localdomain> (raw)
In-Reply-To: <1376979054-2883-2-git-send-email-anand.jain@oracle.com>
On Tue, Aug 20, 2013 at 02:10:54PM +0800, Anand Jain wrote:
> now threads can return BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS
> as defined in btrfs.h for the dev excl operation error in
> the FS, which means with this kernel would stop logging
> (almost an user error) into the /var/log/messages
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/ioctl.c | 12 ++++--------
> include/uapi/linux/btrfs.h | 3 +--
> 2 files changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 107c5f4..89f346c 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -1382,9 +1382,8 @@ static noinline int btrfs_ioctl_resize(struct file *file,
>
> if (atomic_xchg(&root->fs_info->mutually_exclusive_operation_running,
> 1)) {
> - pr_info("btrfs: dev add/delete/balance/replace/resize operation in progress\n");
> mnt_drop_write_file(file);
> - return -EINVAL;
> + return BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> }
>
> mutex_lock(&root->fs_info->volume_mutex);
> @@ -2346,8 +2345,7 @@ static long btrfs_ioctl_add_dev(struct btrfs_root *root, void __user *arg)
>
> if (atomic_xchg(&root->fs_info->mutually_exclusive_operation_running,
> 1)) {
> - pr_info("btrfs: dev add/delete/balance/replace/resize operation in progress\n");
> - return -EINVAL;
> + return BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> }
>
> mutex_lock(&root->fs_info->volume_mutex);
> @@ -3638,8 +3636,7 @@ static long btrfs_ioctl_dev_replace(struct btrfs_root *root, void __user *arg)
> if (atomic_xchg(
> &root->fs_info->mutually_exclusive_operation_running,
> 1)) {
> - pr_info("btrfs: dev add/delete/balance/replace/resize operation in progress\n");
> - ret = -EINPROGRESS;
> + ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> } else {
> ret = btrfs_dev_replace_start(root, p);
> atomic_set(
> @@ -3883,8 +3880,7 @@ again:
> } else {
> /* this is (1) */
> mutex_unlock(&fs_info->balance_mutex);
> - pr_info("btrfs: dev add/delete/balance/replace/resize operation in progress\n");
> - ret = -EINVAL;
> + ret = BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS;
> goto out;
> }
>
> diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
> index 90d7bd9..182305f 100644
> --- a/include/uapi/linux/btrfs.h
> +++ b/include/uapi/linux/btrfs.h
> @@ -505,8 +505,7 @@ static inline char *btrfs_err_str(enum btrfs_err_code err_code)
> case BTRFS_ERROR_DEV_ONLY_WRITABLE:
> return "unable to remove the only writeable device";
> case BTRFS_ERROR_DEV_EXCL_RUN_IN_PROGRESS:
> - return "add/delete/balance/replace/resize operation "\
> - "in progress";
> + return "add/delete/balance/replace/resize operation in progress";
> default:
> return NULL;
This is an unnecessary change. Thanks,
Josef
next prev parent reply other threads:[~2013-08-20 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 6:10 [PATCH] btrfs-progs: use btrfs error code for kernel errors Anand Jain
2013-08-20 6:10 ` [PATCH] btrfs: return btrfs error code for dev excl ops err Anand Jain
2013-08-20 18:34 ` Josef Bacik [this message]
2013-08-21 3:47 ` Anand Jain
2013-09-02 16:59 ` David Sterba
2013-08-21 3:44 ` [PATCH v2] " Anand Jain
2013-09-06 9:38 ` [PATCH 3/3] btrfs-progs: use btrfs error code for kernel errors Anand Jain
2013-09-13 11:35 ` [PATCH] " 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=20130820183405.GH3990@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=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).