For various error conditions the bfa driver just returns
'DID_ERROR', which carries no information at all about the
actual source of error.
This patch updates the error handling to return a correct
error code, depending on the type of error occurred.

Signed-off-by: Hannes Reinecke <h...@suse.de>
---
 drivers/scsi/bfa/bfad_im.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/scsi/bfa/bfad_im.c b/drivers/scsi/bfa/bfad_im.c
index 9967f9c..f067332 100644
--- a/drivers/scsi/bfa/bfad_im.c
+++ b/drivers/scsi/bfa/bfad_im.c
@@ -73,9 +73,14 @@ bfa_cb_ioim_done(void *drv, struct bfad_ioim_s *dio,
 
                break;
 
-       case BFI_IOIM_STS_ABORTED:
        case BFI_IOIM_STS_TIMEDOUT:
+               host_status = DID_TIME_OUT;
+               cmnd->result = ScsiResult(host_status, 0);
+               break;
        case BFI_IOIM_STS_PATHTOV:
+               host_status = DID_TRANSPORT_DISRUPTED;
+               cmnd->result = ScsiResult(host_status, 0);
+               break;
        default:
                host_status = DID_ERROR;
                cmnd->result = ScsiResult(host_status, 0);
-- 
1.7.12.4

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to