From: Dan Carpenter <dan.carpenter@oracle.com>
To: linux-sctp@vger.kernel.org
Subject: re: sctp: Add GSO support
Date: Mon, 06 Jun 2016 20:16:46 +0000 [thread overview]
Message-ID: <20160606201646.GA5425@mwanda> (raw)
Hello Marcelo Ricardo Leitner,
This is a semi-automatic email about new static checker warnings.
The patch 90017accff61: "sctp: Add GSO support" from Jun 2, 2016,
leads to the following Smatch complaint:
net/sctp/output.c:122 sctp_packet_config()
error: we previously assumed 'asoc' could be null (see line 94)
net/sctp/output.c
93
94 if (asoc && tp->dst) {
^^^^
New test.
95 struct sock *sk = asoc->base.sk;
96
97 rcu_read_lock();
98 if (__sk_dst_get(sk) != tp->dst) {
99 dst_hold(tp->dst);
100 sk_setup_caps(sk, tp->dst);
101 }
102
103 if (sk_can_gso(sk)) {
104 struct net_device *dev = tp->dst->dev;
105
106 packet->max_size = dev->gso_max_size;
107 } else {
108 packet->max_size = asoc->pathmtu;
109 }
110 rcu_read_unlock();
111
112 } else {
113 packet->max_size = tp->pathmtu;
114 }
115
116 if (ecn_capable && sctp_packet_empty(packet)) {
117 struct sctp_chunk *chunk;
118
119 /* If there a is a prepend chunk stick it on the list before
120 * any other chunks get appended.
121 */
122 chunk = sctp_get_ecne_prepend(asoc);
^^^^
New unchecked dereference. It's possible that maybe checking
ecn_capable and sctp_packet_empty() implies that "asoc" is non-NULL but
it's not obvious from a glance. Anyway, just let me know if that's the
case.
123 if (chunk)
124 sctp_packet_append_chunk(packet, chunk);
regards,
dan carpenter
next reply other threads:[~2016-06-06 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 20:16 Dan Carpenter [this message]
2016-06-06 20:26 ` sctp: Add GSO support marcelo.leitner
2016-06-06 20:42 ` Dan Carpenter
2016-06-06 21:07 ` marcelo.leitner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160606201646.GA5425@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-sctp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).