Searched hist:"907 c07d4" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/drivers/scsi/libfc/ |
H A D | fc_lport.c | 907c07d4 Fri Oct 28 13:34:23 CDT 2011 Vasu Dev <vasu.dev@intel.com> [SCSI] libfc: improve flogi retries to avoid lport stuck
Adds more cases to do flogi retry, now also retry on getting bad response due to either no ELS response or flogi response payload length not large enough. In those cases flogi was not retried and that was leaving lport offline.
Signed-off-by: Vasu Dev <vasu.dev@intel.com> Tested-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com> Signed-off-by: Yi Zou <yi.zou@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> 907c07d4 Fri Oct 28 13:34:23 CDT 2011 Vasu Dev <vasu.dev@intel.com> [SCSI] libfc: improve flogi retries to avoid lport stuck Adds more cases to do flogi retry, now also retry on getting bad response due to either no ELS response or flogi response payload length not large enough. In those cases flogi was not retried and that was leaving lport offline. Signed-off-by: Vasu Dev <vasu.dev@intel.com> Tested-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com> Signed-off-by: Yi Zou <yi.zou@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com>
|
/openbmc/linux/drivers/scsi/fcoe/ |
H A D | fcoe.c | 907c07d4 Fri Oct 28 13:34:23 CDT 2011 Vasu Dev <vasu.dev@intel.com> [SCSI] libfc: improve flogi retries to avoid lport stuck
Adds more cases to do flogi retry, now also retry on getting bad response due to either no ELS response or flogi response payload length not large enough. In those cases flogi was not retried and that was leaving lport offline.
Signed-off-by: Vasu Dev <vasu.dev@intel.com> Tested-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com> Signed-off-by: Yi Zou <yi.zou@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> 907c07d4 Fri Oct 28 13:34:23 CDT 2011 Vasu Dev <vasu.dev@intel.com> [SCSI] libfc: improve flogi retries to avoid lport stuck Adds more cases to do flogi retry, now also retry on getting bad response due to either no ELS response or flogi response payload length not large enough. In those cases flogi was not retried and that was leaving lport offline. Signed-off-by: Vasu Dev <vasu.dev@intel.com> Tested-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com> Signed-off-by: Yi Zou <yi.zou@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com>
|