hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[SCSI] libfc: use DID_ERROR when we have internall aborted command 

If we aborted a command, because it timed out we should not use
DID_ABORT. It will fail the command right away back to the upper
layer. We want to use something that indicated that the problem
did not complete normally, but it was not a fatal problem.

Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
This commit is contained in:
Mike Christie 2009-05-06 10:52:23 -07:00 committed by James Bottomley
parent 0f4915398a
commit d5e6054a0a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/scsi/libfc/fc_fcp.c
View File

@ -1896,7 +1896,7 @@ static void fc_io_compl(struct fc_fcp_pkt *fsp)
sc_cmd->result = (DID_ERROR << 16) | fsp->cdb_status; sc_cmd->result = (DID_ERROR << 16) | fsp->cdb_status;
break; break;
case FC_CMD_ABORTED: case FC_CMD_ABORTED:
sc_cmd->result = (DID_ABORT << 16) | fsp->io_status; sc_cmd->result = (DID_ERROR << 16) | fsp->io_status;
break; break;
case FC_CMD_TIME_OUT: case FC_CMD_TIME_OUT:
sc_cmd->result = (DID_BUS_BUSY << 16) | fsp->io_status; sc_cmd->result = (DID_BUS_BUSY << 16) | fsp->io_status;