linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] btrfs: return EPERM in btrfs_rm_device()
@ 2013-03-02  7:13 Jerry Snitselaar
  2013-03-02 18:04 ` Ilya Dryomov
  0 siblings, 1 reply; 2+ messages in thread
From: Jerry Snitselaar @ 2013-03-02  7:13 UTC (permalink / raw)
  To: linux-btrfs; +Cc: chris.mason, dsterba, linux-kernel

Currently there are error paths in btrfs_rm_device() where EINVAL is
returned telling the user they passed an invalid argument even though
they passed a valid device. Change to return EPERM instead as the
operation is not permitted.

Signed-off-by: Jerry Snitselaar <jerry.snitselaar@oracle.com>
---
 fs/btrfs/volumes.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 5cbb7f4..3e1586c 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -1392,14 +1392,14 @@ int btrfs_rm_device(struct btrfs_root *root, char *device_path)
 	if ((all_avail & BTRFS_BLOCK_GROUP_RAID10) && num_devices <= 4) {
 		printk(KERN_ERR "btrfs: unable to go below four devices "
 		       "on raid10\n");
-		ret = -EINVAL;
+		ret = -EPERM;
 		goto out;
 	}
 
 	if ((all_avail & BTRFS_BLOCK_GROUP_RAID1) && num_devices <= 2) {
 		printk(KERN_ERR "btrfs: unable to go below two "
 		       "devices on raid1\n");
-		ret = -EINVAL;
+		ret = -EPERM;
 		goto out;
 	}
 
@@ -1449,14 +1449,14 @@ int btrfs_rm_device(struct btrfs_root *root, char *device_path)
 
 	if (device->is_tgtdev_for_dev_replace) {
 		pr_err("btrfs: unable to remove the dev_replace target dev\n");
-		ret = -EINVAL;
+		ret = -EPERM;
 		goto error_brelse;
 	}
 
 	if (device->writeable && root->fs_info->fs_devices->rw_devices == 1) {
 		printk(KERN_ERR "btrfs: unable to remove the only writeable "
 		       "device\n");
-		ret = -EINVAL;
+		ret = -EPERM;
 		goto error_brelse;
 	}
 
-- 
1.8.2.rc1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] btrfs: return EPERM in btrfs_rm_device()
  2013-03-02  7:13 [PATCH] btrfs: return EPERM in btrfs_rm_device() Jerry Snitselaar
@ 2013-03-02 18:04 ` Ilya Dryomov
  0 siblings, 0 replies; 2+ messages in thread
From: Ilya Dryomov @ 2013-03-02 18:04 UTC (permalink / raw)
  To: Jerry Snitselaar; +Cc: linux-btrfs, chris.mason, dsterba, linux-kernel

On Sat, Mar 02, 2013 at 12:13:59AM -0700, Jerry Snitselaar wrote:
> Currently there are error paths in btrfs_rm_device() where EINVAL is
> returned telling the user they passed an invalid argument even though
> they passed a valid device. Change to return EPERM instead as the
> operation is not permitted.
> 
> Signed-off-by: Jerry Snitselaar <jerry.snitselaar@oracle.com>
> ---
>  fs/btrfs/volumes.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 5cbb7f4..3e1586c 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -1392,14 +1392,14 @@ int btrfs_rm_device(struct btrfs_root *root, char *device_path)
>  	if ((all_avail & BTRFS_BLOCK_GROUP_RAID10) && num_devices <= 4) {
>  		printk(KERN_ERR "btrfs: unable to go below four devices "
>  		       "on raid10\n");
> -		ret = -EINVAL;
> +		ret = -EPERM;
>  		goto out;
>  	}
>  
>  	if ((all_avail & BTRFS_BLOCK_GROUP_RAID1) && num_devices <= 2) {
>  		printk(KERN_ERR "btrfs: unable to go below two "
>  		       "devices on raid1\n");
> -		ret = -EINVAL;
> +		ret = -EPERM;
>  		goto out;
>  	}
>  
> @@ -1449,14 +1449,14 @@ int btrfs_rm_device(struct btrfs_root *root, char *device_path)
>  
>  	if (device->is_tgtdev_for_dev_replace) {
>  		pr_err("btrfs: unable to remove the dev_replace target dev\n");
> -		ret = -EINVAL;
> +		ret = -EPERM;
>  		goto error_brelse;
>  	}
>  
>  	if (device->writeable && root->fs_info->fs_devices->rw_devices == 1) {
>  		printk(KERN_ERR "btrfs: unable to remove the only writeable "
>  		       "device\n");
> -		ret = -EINVAL;
> +		ret = -EPERM;

I don't think returning EPERM in these cases is any better than EINVAL.
FWIW, many other btrfs ioctls, especially balance, suffer from this as
well.  What we really need is some kind of error message delivery
system, but that's not going to happen any time soon...

Thanks,

		Ilya

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-03-02 18:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-02  7:13 [PATCH] btrfs: return EPERM in btrfs_rm_device() Jerry Snitselaar
2013-03-02 18:04 ` Ilya Dryomov

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).