On 03/07/2013 02:13 PM, Jeremy Linton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 3/7/2013 1:19 PM, Mike Christie wrote: >> What happens for lpfc? It seems __fc_remote_port_delete ends up calling the >> fast io fail code right away and that sets FC_RPORT_FAST_FAIL_TIMEDOUT. We >> will then call lpfc_terminate_rport_io which only will send aborts for the >> commands. We will then call fc_block_scsi_eh above and that returns >> FAST_IO_FAIL and we will pass that back up to the scsi eh right away. > > > For lpfc, you never get to the code. Or rather when I was testing it, I > couldn't find any way to propagate an error beyond the initial > lpfc_reset_flush_io_context() call in lpfc_device_reset_handler(). > > That call pretty much always returns success indpependent of the remote > device because the firmware acks the context clear aborts, resulting in the > outstanding iocb count being zero (independent of both the mid layer status > and the actual device state). > Your lpfc patch fixes that right? -- 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
