nvmet-fcloop: remove use of FC-specific error codes

The FC-NVME transport loopback test module used the FC-specific error
codes in cases where it emulated a transport abort case. Instead of
using the FC-specific values, now use a generic value (NVME_SC_INTERNAL).

Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c
index 1cb9847ec261182dd5fdc6da836d14fa1503ad9b..1fd1afbb8b2a2d04b468c7a41cd37e07c2e6a677 100644 (file)
--- a/drivers/nvme/target/fcloop.c
+++ b/drivers/nvme/target/fcloop.c
@@ -576,7 +576,7 @@ fcloop_tgt_fcp_abort(struct nvmet_fc_target_port *tgtport,
        tfcp_req->aborted = true;
        spin_unlock(&tfcp_req->reqlock);
 
-       tfcp_req->status = NVME_SC_FC_TRANSPORT_ABORTED;
+       tfcp_req->status = NVME_SC_INTERNAL;
 
        /*
         * nothing more to do. If io wasn't active, the transport should