From: Tan Xiaojun <tanxiaojun@huawei.com>
To: <davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
<jmorris@namei.org>, <yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
<aduyck@mirantis.com>, <hkchu@google.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: IP ID check (flush_id) in inet_gro_receive is necessary or not?
Date: Tue, 28 Jun 2016 12:40:01 +0800 [thread overview]
Message-ID: <5771FFA1.3050306@huawei.com> (raw)
Hi everyone,
I'm sorry to bother you. But I was confused.
The IP ID check (flush_id) in inet_gro_receive is only used by tcp_gro_receive, and in tcp_gro_receive we have tcphdr check to ensure the order of skbs,
like below:
flush |= (__force int)(th->ack_seq ^ th2->ack_seq);
flush |= (ntohl(th2->seq) + skb_gro_len(p)) ^ ntohl(th->seq);
So if I remove the IP ID check in inet_gro_receive, there will be a problem ? And under what circumstances ?
Thanks.
Xiaojun.
next reply other threads:[~2016-06-28 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 4:40 Tan Xiaojun [this message]
2016-06-28 4:57 ` IP ID check (flush_id) in inet_gro_receive is necessary or not? Eric Dumazet
2016-06-28 7:44 ` Tan Xiaojun
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=5771FFA1.3050306@huawei.com \
--to=tanxiaojun@huawei.com \
--cc=aduyck@mirantis.com \
--cc=davem@davemloft.net \
--cc=hkchu@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).