From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Linux Kernel Developers <linux-kernel@vger.kernel.org>
Cc: "Linux Kernel Network Developers" <netdev@vger.kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: query: redundant tcp header length checks?
Date: Sun, 10 Jan 2010 08:02:57 -0500 [thread overview]
Message-ID: <4B49D001.4000302@gmail.com> (raw)
On a related note, back on Nov 10th, Ilpo brought to my attention --
*hidden* inside the pskb_may_pull() -- the tcp header length is range
checked for being too short (skb->len < th->doff * 4).
tcp_v4_rcv()
...
1585 if (!pskb_may_pull(skb, th->doff * 4))
1586 goto discard_it;
1587
But the next comment in tcp_ipv4.c (missing from tcp_ipv6.c) says:
1588 /* An explanation is required here, I think.
1589 * Packet length and doff are validated by header prediction,
1590 * provided case of th->doff==0 is eliminated.
1591 * So, we defer the checks. */
That's not correct anymore, as the checks aren't deferred! But the
redundant deferred checks _are_ still present in tcp_input.c:
tcp_rcv_established()
...
5210 if (len <= tcp_header_len) {
5211 /* Bulk data transfer: sender */
5212 if (len == tcp_header_len) {
...
5229 } else { /* Header too small */
5230 TCP_INC_STATS_BH(sock_net(sk), TCP_MIB_INERRS);
5231 goto discard;
5232 }
Also:
5325 slow_path:
5326 if (len < (th->doff << 2) || tcp_checksum_complete_user(sk, skb))
5327 goto csum_error;
Apparently tcp_rcv_established() might be called through some other path
that requires this extra header length checking?
Its callers also have another reference, for example in tcp_ipv4.c:
2432 .backlog_rcv = tcp_v4_do_rcv,
And tcp_ipv6.c:
213 sk->sk_backlog_rcv = tcp_v4_do_rcv;
223 sk->sk_backlog_rcv = tcp_v6_do_rcv;
1302 newsk->sk_backlog_rcv = tcp_v4_do_rcv;
2073 .backlog_rcv = tcp_v6_do_rcv,
Can anybody explain these?
next reply other threads:[~2010-01-10 13:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 13:02 William Allen Simpson [this message]
2010-01-12 10:05 ` [PATCH] tcp: harmonize tcp_vx_rcv header length assumptions William Allen Simpson
2010-01-12 10:46 ` Eric Dumazet
2010-01-12 17:11 ` William Allen Simpson
2010-01-13 9:50 ` William Allen Simpson
2010-01-12 17:14 ` William Allen Simpson
2010-01-13 10:48 ` [PATCH v4] " William Allen Simpson
2010-01-13 11:56 ` Andi Kleen
2010-01-13 15:36 ` William Allen Simpson
2010-01-13 15:53 ` Andi Kleen
2010-01-13 16:40 ` [PATCH] Makefile: Document ability to make file.lst and file.S Joe Perches
2010-01-13 17:14 ` Andi Kleen
2010-01-13 17:31 ` Joe Perches
2010-01-13 19:51 ` William Allen Simpson
2010-01-14 3:26 ` Américo Wang
2010-01-18 12:29 ` Michal Marek
2010-01-13 19:49 ` [PATCH v4] tcp: harmonize tcp_vx_rcv header length assumptions William Allen Simpson
2010-01-13 20:19 ` Andi Kleen
2010-01-13 21:13 ` William Allen Simpson
2010-01-14 1:03 ` Joe Perches
2010-01-14 8:39 ` Patrick McHardy
2010-01-14 15:02 ` William Allen Simpson
2010-01-14 15:10 ` [PATCH v5] " William Allen Simpson
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=4B49D001.4000302@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).