summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorAlex Elder <elder@dreamhost.com>2012-11-01 14:39:26 +0100
committerAlex Elder <elder@inktank.com>2012-12-17 19:07:32 +0100
commitb8f5c6edca34ff441e1ccdec68828e933a1b905b (patch)
tree4c0c7b5f3d61ce897e0cc7b62d9312c59bb43563 /drivers
parentrbd: remove linger unconditionally (diff)
downloadlinux-b8f5c6edca34ff441e1ccdec68828e933a1b905b.tar.xz
linux-b8f5c6edca34ff441e1ccdec68828e933a1b905b.zip
rbd: don't use ENOTSUPP
ENOTSUPP is not a standard errno (it shows up as "Unknown error 524" in an error message). This is what was getting produced when the the local rbd code does not implement features required by a discovered rbd image. Change the error code returned in this case to ENXIO. Signed-off-by: Alex Elder <elder@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/block/rbd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index ce26b749ede0..4daa400c13aa 100644
--- a/drivers/block/rbd.c
+++ b/drivers/block/rbd.c
@@ -2456,7 +2456,7 @@ static int _rbd_dev_v2_snap_features(struct rbd_device *rbd_dev, u64 snap_id,
incompat = le64_to_cpu(features_buf.incompat);
if (incompat & ~RBD_FEATURES_ALL)
- return -ENOTSUPP;
+ return -ENXIO;
*snap_features = le64_to_cpu(features_buf.features);