SCTP: Uncomfirmed transports can't become Inactive
Do not set Unconfirmed transports to Inactive state. This may result in an inactive association being destroyed since we start counting errors on "inactive" transports against the association. This was found at the SCTP interop event. Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
This commit is contained in:
parent
2772b495ef
commit
cc75689a4c
|
@ -727,7 +727,12 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
|
|||
break;
|
||||
|
||||
case SCTP_TRANSPORT_DOWN:
|
||||
transport->state = SCTP_INACTIVE;
|
||||
/* if the transort was never confirmed, do not transition it
|
||||
* to inactive state.
|
||||
*/
|
||||
if (transport->state != SCTP_UNCONFIRMED)
|
||||
transport->state = SCTP_INACTIVE;
|
||||
|
||||
spc_state = SCTP_ADDR_UNREACHABLE;
|
||||
break;
|
||||
|
||||
|
|
Loading…
Reference in New Issue