tipc: separate link starting event from link timeout event
When a new link instance is created, it is trigged to start by sending it a TIPC_STARTING_EVT, whereafter a regular link reset is applied to it. The starting event is codewise treated as a timeout event, and prompts a link RESET message to be sent to the peer node, carrying a link session identifier. The later link_reset() call nudges this session identifier, whereafter all subsequent RESET messages will be sent out with the new identifier. The latter session number overrides the former, causing the peer to unconditionally accept it irrespective of its current working state. We don't think that this causes any problem, but it is not in accordance with the protocol spec, and may cause confusion when debugging TIPC sessions. To avoid this, we make the starting event distinct from the subsequent timeout events, by not allowing the former to send out any RESET message. This eliminates the described problem. Reviewed-by: Erik Hugne <erik.hugne@ericsson.com> Reviewed-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
b45db71b52
commit
af9946fde9
|
@ -649,7 +649,9 @@ static void link_state_event(struct tipc_link *l_ptr, unsigned int event)
|
|||
break;
|
||||
case STARTING_EVT:
|
||||
l_ptr->flags |= LINK_STARTED;
|
||||
/* fall through */
|
||||
l_ptr->fsm_msg_cnt++;
|
||||
link_set_timer(l_ptr, cont_intv);
|
||||
break;
|
||||
case TIMEOUT_EVT:
|
||||
tipc_link_proto_xmit(l_ptr, RESET_MSG, 0, 0, 0, 0, 0);
|
||||
l_ptr->fsm_msg_cnt++;
|
||||
|
|
Loading…
Reference in New Issue