On Fri, 2017-02-24 at 08:15 +0100, Hannes Reinecke wrote: > scsi_abort_command() (ie the call which triggers async aborts) is only > called if the .eh_timed_out() callback returns BLK_EH_NOT_HANDLED. > So during reconnects we will not schedule any calls to async aborts. > We _might_ have scheduled an async abort prior to a call to > srp_reconnect_rport(), but that would be equivalent with calling > srp_reconnect_rport() with commands still in flight. > Is that even possible? > If so, how do you handle these commands after reconnect returns? > Any I_T_L nexus will be gone from the target, right? srp_reconnect_rport() can proceed while commands are in flight. What will happen is that no response will be received for the commands that are in flight and hence that these commands will time out at the initiator side. However, any newly submitted commands will be processed normally. Bart.
