Commit 061079ac authored by zhuyj's avatar zhuyj Committed by David S. Miller
Browse files

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: default avatarDeepak Khandelwal <khandelwal.deepak.1987@gmail.com>
Suggested-by: default avatarVlad Yasevich <vyasevich@gmail.com>
Suggested-by: default avatarMichael Tuexen <tuexen@fh-muenster.de>
Suggested-by: default avatarDaniel Borkmann <dborkman@redhat.com>
Signed-off-by: default avatarZhu Yanjun <Yanjun.Zhu@windriver.com>
Acked-by: default avatarVlad Yasevich <vyasevich@gmail.com>
Acked-by: default avatarDaniel Borkmann <dborkman@redhat.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 7c3afd85
...@@ -813,6 +813,7 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, ...@@ -813,6 +813,7 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
else { else {
dst_release(transport->dst); dst_release(transport->dst);
transport->dst = NULL; transport->dst = NULL;
ulp_notify = false;
} }
spc_state = SCTP_ADDR_UNREACHABLE; spc_state = SCTP_ADDR_UNREACHABLE;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment