James Smart wrote:
Revert the target busy response in favor of the transport disrupted
response for node state transitions.
Do we hit this code path if some other process has set the lpfc ndlp
state and is calling fc_remote_port_delete? Or can we end up hitting
this when the fc rport is FC_PORTSTATE_ONLINE (and not going to get
deleted)? If the former, I had thought target busy was best because I
thought it was just when we race with the fc_remote_port_delete and the
ndlp change, and so I thought in this case we just wanted to fail with
target busy to reflect that it was due to the race and not the transport
problem that caused the rport deletion. That may not be logical or right
though :) I do not care either way. I am mostly asking because if we go
your route then I will send a patch to change the other fc drivers so
they all do the same thing for this type of case.
Signed-off-by: James Smart <james.smart@xxxxxxxxxx>
---
lpfc_scsi.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff -upNr a/drivers/scsi/lpfc/lpfc_scsi.c b/drivers/scsi/lpfc/lpfc_scsi.c
--- a/drivers/scsi/lpfc/lpfc_scsi.c 2008-09-06 11:54:50.000000000 -0400
+++ b/drivers/scsi/lpfc/lpfc_scsi.c 2008-09-07 10:28:20.000000000 -0400
@@ -1071,8 +1071,10 @@ lpfc_queuecommand(struct scsi_cmnd *cmnd
* Catch race where our node has transitioned, but the
* transport is still transitioning.
*/
- if (!ndlp || !NLP_CHK_NODE_ACT(ndlp))
- goto out_target_busy;
+ if (!ndlp || !NLP_CHK_NODE_ACT(ndlp)) {
+ cmnd->result = ScsiResult(DID_TRANSPORT_DISRUPTED, 0);
+ goto out_fail_command;
+ }
lpfc_cmd = lpfc_get_scsi_buf(phba);
if (lpfc_cmd == NULL) {
@@ -1118,8 +1120,6 @@ lpfc_queuecommand(struct scsi_cmnd *cmnd
lpfc_release_scsi_buf(phba, lpfc_cmd);
out_host_busy:
return SCSI_MLQUEUE_HOST_BUSY;
- out_target_busy:
- return SCSI_MLQUEUE_TARGET_BUSY;
out_fail_command:
done(cmnd);
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
