sctp: not send SCTP_PEER_ADDR_CHANGE notifications with failed probe

Since the transport has always been in state SCTP_UNCONFIRMED, it
therefore wasn't active before and hasn't been used before, and it
always has been, so it is unnecessary to bug the user with a
notification.

Reported-by: Deepak Khandelwal <[email protected]>
Suggested-by: Vlad Yasevich <[email protected]>
Suggested-by: Michael Tuexen <[email protected]>
Suggested-by: Daniel Borkmann <[email protected]>
Signed-off-by: Zhu Yanjun <[email protected]>
Acked-by: Vlad Yasevich <[email protected]>
Acked-by: Daniel Borkmann <[email protected]>
Signed-off-by: David S. Miller <[email protected]>

Author: zhuyj

net/sctp/associola.c

@@ -813,6 +813,7 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
 		else {
 			dst_release(transport->dst);
 			transport->dst = NULL;
+			ulp_notify = false;
 		}
 
 		spc_state = SCTP_ADDR_UNREACHABLE;