From: Or Gerlitz <or.gerlitz@gmail.com>
To: "H.K. Jerry Chu" <hkchu@google.com>
Cc: Eric Dumazet <edumazet@google.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net-gre-gro: Fix a bug that breaks the forwarding path
Date: Fri, 28 Feb 2014 00:25:46 +0200 [thread overview]
Message-ID: <CAJZOPZKy7w-q5+pp=FgCs8LdQL6e16zAiJr89VMkh+h7obAArg@mail.gmail.com> (raw)
In-Reply-To: <1393536377-32243-1-git-send-email-hkchu@google.com>
On Thu, Feb 27, 2014 at 11:26 PM, H.K. Jerry Chu <hkchu@google.com> wrote:
> From: Jerry Chu <hkchu@google.com>
>
> I stumbled across a bug that was introduced by my own GRE-GRO
> patch (bf5a755f5e9186406bbf50f4087100af5bd68e40
> net-gre-gro: Add GRE support to the GRO stack) submitted a while
> back that breaks the forwarding path because various GSO related
> fields were not set. This will cause on the egress path either
> the GSO code to fail, or a GRE-TSO capable (NETIF_F_GSO_GRE)
> NICs to choke. The following fix has been tested for both cases.
>
> Signed-off-by: H.K. Jerry Chu <hkchu@google.com>
> ---
> net/core/dev.c | 2 ++
> net/ipv4/af_inet.c | 3 +++
> net/ipv4/gre_offload.c | 3 +++
> net/ipv4/tcp_offload.c | 2 +-
> net/ipv6/tcpv6_offload.c | 2 +-
> 5 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index b1b0c8d..75517d8 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4045,6 +4045,8 @@ static void napi_reuse_skb(struct napi_struct *napi, struct sk_buff *skb)
> skb->vlan_tci = 0;
> skb->dev = napi->dev;
> skb->skb_iif = 0;
> + skb->encapsulation = 0;
> + skb_shinfo(skb)->gso_type = 0;
>
> napi->skb = skb;
> }
> diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> index ecd2c3f..68229ca 100644
> --- a/net/ipv4/af_inet.c
> +++ b/net/ipv4/af_inet.c
> @@ -1431,6 +1431,9 @@ static int inet_gro_complete(struct sk_buff *skb, int nhoff)
> int proto = iph->protocol;
> int err = -ENOSYS;
>
> + if (skb->encapsulation)
> + skb_set_inner_network_header(skb, nhoff);
> +
Note that packets (e.g those who are UDP encapsulated) will pass here
twice, once for the external IP header and once for the internal, so
if the driver marks the encapsulation sign the inner header setting
will happen twice, is that what we want?
> csum_replace2(&iph->check, iph->tot_len, newlen);
> iph->tot_len = newlen;
next prev parent reply other threads:[~2014-02-27 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:26 [PATCH] net-gre-gro: Fix a bug that breaks the forwarding path H.K. Jerry Chu
2014-02-27 22:25 ` Or Gerlitz [this message]
2014-02-27 23:39 ` Jerry Chu
2014-02-28 21:56 ` David Miller
2014-03-03 9:30 ` Or Gerlitz
2014-03-04 16:13 ` Or Gerlitz
2014-03-04 22:13 ` Jerry Chu
2014-03-04 22:53 ` Joseph Gasparakis
2014-03-04 23:11 ` Jerry Chu
2014-03-05 1:01 ` Joseph Gasparakis
2014-03-05 0:54 ` Jerry Chu
2014-03-05 1:27 ` Joseph Gasparakis
2014-03-05 1:14 ` Alexei Starovoitov
2014-03-04 22:36 ` Joseph Gasparakis
2014-03-05 0:50 ` Tom Herbert
2014-03-05 1:46 ` Joseph Gasparakis
2014-03-05 20:47 ` Or Gerlitz
2014-03-06 16:42 ` Joseph Gasparakis
2014-03-06 16:30 ` Hannes Frederic Sowa
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='CAJZOPZKy7w-q5+pp=FgCs8LdQL6e16zAiJr89VMkh+h7obAArg@mail.gmail.com' \
--to=or.gerlitz@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkchu@google.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
/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).