summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/qedf/qedf_els.c
diff options
context:
space:
mode:
authorChad Dupuis2017-05-31 15:33:56 +0200
committerMartin K. Petersen2017-06-13 02:48:06 +0200
commitb09fdc3aac6acc20587713e306692b12d31a2008 (patch)
treebf7d15c5cf973a891aaed8d519ffb5d4fce81b7a /drivers/scsi/qedf/qedf_els.c
parentscsi: qedf: Use same logic for SCSI host reset and FC lip_reset. (diff)
downloadkernel-qcow2-linux-b09fdc3aac6acc20587713e306692b12d31a2008.tar.gz
kernel-qcow2-linux-b09fdc3aac6acc20587713e306692b12d31a2008.tar.xz
kernel-qcow2-linux-b09fdc3aac6acc20587713e306692b12d31a2008.zip
scsi: qedf: Add bus_reset No-op.
We need to add a bus reset no-op as without it some of the LUNs attached to a vport may go offline when the error handler escalates to host reset due to not having a bus reset handler in the driver. What happens is we escalate to host reset which does a soft link down/link up to reset the adapter. However with multiple vports attached it's been observed that if the vports do log back into the target within 5 seconds, the SCSI layer offlines the devices most likely due to a TUR timing out to verify that the device is online. Adding a bus reset handler will cause the TUR to be sent after the bus reset handler where the devices will still be online if the bus reset is initiated by sg_reset (which is the case in the test that was failing). The bus reset will succeed and not needlessly bring the device offline/online. Signed-off-by: Chad Dupuis <chad.dupuis@cavium.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/qedf/qedf_els.c')
0 files changed, 0 insertions, 0 deletions