瀏覽代碼

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>
James Smart 8 年之前
父節點
當前提交
fc9608e8b4
共有 1 個文件被更改,包括 1 次插入1 次删除
  1. 1 1
      drivers/nvme/target/fcloop.c

+ 1 - 1
drivers/nvme/target/fcloop.c

@@ -576,7 +576,7 @@ fcloop_tgt_fcp_abort(struct nvmet_fc_target_port *tgtport,
 	tfcp_req->aborted = true;
 	tfcp_req->aborted = true;
 	spin_unlock(&tfcp_req->reqlock);
 	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
 	 * nothing more to do. If io wasn't active, the transport should