[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5404651c2e80731082fd1a1cbf94d9f3c765dc34.1501825111.git.fthain@telegraphics.com.au>
Date: Fri, 4 Aug 2017 01:43:20 -0400 (EDT)
From: Finn Thain <fthain@...egraphics.com.au>
To: "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
David Miller <davem@...emloft.net>,
Hannes Reinecke <hare@...e.com>, Meelis Roos <mroos@...ux.ee>,
Michael Schmitz <schmitzmic@...il.com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH 5/5] scsi/esp_scsi: Always clear msg_out_len after MESSAGE OUT
phase
After sending a message, always clear esp->msg_out_len. Otherwise,
eh_abort_handler may subsequently fail to send an ABORT TASK SET
message.
Tested-by: Stan Johnson <userm57@...oo.com>
Signed-off-by: Finn Thain <fthain@...egraphics.com.au>
---
drivers/scsi/esp_scsi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/scsi/esp_scsi.c b/drivers/scsi/esp_scsi.c
index 4d1e08a87274..c3fc34b9964d 100644
--- a/drivers/scsi/esp_scsi.c
+++ b/drivers/scsi/esp_scsi.c
@@ -1951,6 +1951,8 @@ static int esp_process_event(struct esp *esp)
scsi_esp_cmd(esp, ESP_CMD_NULL);
}
+ esp->msg_out_len = 0;
+
esp_event(esp, ESP_EVENT_CHECK_PHASE);
goto again;
case ESP_EVENT_MSGIN:
--
2.13.0
Powered by blists - more mailing lists