summaryrefslogtreecommitdiff
path: root/drivers/scsi
diff options
context:
space:
mode:
author <jejb@titanic.il.steeleye.com>2005-04-13 02:49:09 +0400
committerJames Bottomley <jejb@titanic>2005-04-18 21:35:06 +0400
commitbf341919dbc1fbcbb565fb3224c840760ebd9f85 (patch)
tree9ff0bb375ccd709b018eccd6d338bf18b9c898aa /drivers/scsi
parent6f71d9bc025b02a8cbc2be83b0226a7043a507a5 (diff)
downloadlinux-bf341919dbc1fbcbb565fb3224c840760ebd9f85.tar.xz
scsi: add DID_REQUEUE to the error handling
We have a DID_IMM_RETRY to require a retry at once, but we could do with a DID_REQUEUE to instruct the mid-layer to treat this command in the same manner as QUEUE_FULL or BUSY (i.e. halt the submission until another command returns ... or the queue pressure builds if there are no outstanding commands). Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'drivers/scsi')
-rw-r--r--drivers/scsi/scsi_error.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
index 13bac93fc397..203a0812508a 100644
--- a/drivers/scsi/scsi_error.c
+++ b/drivers/scsi/scsi_error.c
@@ -1306,6 +1306,9 @@ int scsi_decide_disposition(struct scsi_cmnd *scmd)
case DID_IMM_RETRY:
return NEEDS_RETRY;
+ case DID_REQUEUE:
+ return ADD_TO_MLQUEUE;
+
case DID_ERROR:
if (msg_byte(scmd->result) == COMMAND_COMPLETE &&
status_byte(scmd->result) == RESERVATION_CONFLICT)