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>

1 files changed, 6 insertions, 1 deletions

diff --git a/net/sctp/associola.c b/net/sctp/associola.c
index 498edb0cd4e5..2ad1caf1ea42 100644
--- a/net/sctp/associola.c
+++ b/net/sctp/associola.c
@@ -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;