summaryrefslogtreecommitdiff
path: root/net/wireless
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2014-03-13 13:45:26 (GMT)
committerDavid S. Miller <davem@davemloft.net>2014-03-13 17:23:52 (GMT)
commit433131ba03c511a84e1fda5669c70cf8b44702e1 (patch)
tree94031203cc2483d344e50fd65249cb69219a1b93 /net/wireless
parent8a83d9396a4945dcaa129b14a725311e5846b2d5 (diff)
downloadlinux-433131ba03c511a84e1fda5669c70cf8b44702e1.tar.xz
net: sctp: remove NULL check in sctp_assoc_update_retran_path
This is basically just to let Coverity et al shut up. Remove an unneeded NULL check in sctp_assoc_update_retran_path(). It is safe to remove it, because in sctp_assoc_update_retran_path() we iterate over the list of transports, our own transport which is asoc->peer.retran_path included. In the iteration, we skip the list head element and transports in state SCTP_UNCONFIRMED. Such transports came from peer addresses received in INIT/INIT-ACK address parameters. They are not yet confirmed by a heartbeat and not available for data transfers. We know however that in the list of transports, even if it contains such elements, it at least contains our asoc->peer.retran_path as well, so even if next to that element, we only encounter SCTP_UNCONFIRMED transports, we are always going to fall back to asoc->peer.retran_path through sctp_trans_elect_best(), as that is for sure not SCTP_UNCONFIRMED as per fbdf501c9374 ("sctp: Do no select unconfirmed transports for retransmissions"). Whenever we call sctp_trans_elect_best() it will give us a non-NULL element back, and therefore when we break out of the loop, we are guaranteed to have a non-NULL transport pointer, and can remove the NULL check. Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Reported-by: Dave Jones <davej@redhat.com> Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/wireless')
0 files changed, 0 insertions, 0 deletions