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>
This commit is contained in:
Родитель
29b3d26ecc
Коммит
fc9608e8b4
|
@ -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
|
||||
|
|
Загрузка…
Ссылка в новой задаче