Hi, iscsi session recovery work is queued by function __iscsi_block_session which is in turn called by iscsi_block_session.
This is the function call sequence i figured out (using sw iscsi over tcp/ip) iscsi_if_recv_msg (ISCSI_UEVENT_STOP_CONN) -> iscsi_sw_tcp_conn_stop -> iscsi_conn_stop -> iscsi_start_session_recovery -> iscsi_block_session This means that the session recovery work is initiated by the user space. What events propageted to user space causes it to initiate this recovery ? A function call sequence would greatly help. Thank you -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/M4X9NT2wA_oJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
