| commit | 4ae0a6c15efcc37e94e3f30e3533bdec03c53126 | |
| author | Mike Christie <michaelc@cs.wisc.edu> | |
| Tue, 9 Mar 2010 20:14:51 +0000 (9 14:14 -0600) | ||
| committer | James Bottomley <James.Bottomley@suse.de> | |
| Sat, 27 Mar 2010 19:02:48 +0000 (27 15:02 -0400) | ||
| tree | df66736300cb0b7eb41622bb19fc57fd553caf57 | treesnapshot (tar.gz zip) |
| parent | b72c40949b0f04728f2993a1434598d3bad094ea | commitdiff |
[SCSI] libiscsi: Fix recovery slowdown regression
We could be failing/stopping a connection due to libiscsi starting
recovery/cleanup, but the xmit path or scsi eh thread path
could be dropping the connection at the same time.
As a result the session->state gets set to failed instead of in
recovery. We end up not blocking the session
and so the replacement timeout never gets started and we only end up
failing the IO when scsi_softirq_done sees that the
cmd has been running for (cmd->allowed + 1) * rq->timeout secs.
We used to fail the IO right away so users are seeing a long
delay when using dm-multipath. This problem was added in
2.6.28.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Cc: stable@kernel.org
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
We could be failing/stopping a connection due to libiscsi starting
recovery/cleanup, but the xmit path or scsi eh thread path
could be dropping the connection at the same time.
As a result the session->state gets set to failed instead of in
recovery. We end up not blocking the session
and so the replacement timeout never gets started and we only end up
failing the IO when scsi_softirq_done sees that the
cmd has been running for (cmd->allowed + 1) * rq->timeout secs.
We used to fail the IO right away so users are seeing a long
delay when using dm-multipath. This problem was added in
2.6.28.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Cc: stable@kernel.org
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
| drivers/scsi/libiscsi.c | diffblobblamehistory |