From: Jerry Chu <hkchu@google.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Tom Herbert <therbert@google.com>,
Eric Dumazet <edumazet@google.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Wolfgang Walter <linux@stwm.de>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net-gre-gro: Fix a bug that breaks the forwarding path
Date: Mon, 14 Jul 2014 14:30:09 -0700 [thread overview]
Message-ID: <CAPshTCiKnKx_P=JLQcgjS36rWmCtSS43XYNJHeif9Z9yP8C36Q@mail.gmail.com> (raw)
In-Reply-To: <CAJZOPZLwiT7LhxDFYdAq=0iU6heSwBQfCvwxXtoAXMqg=eNAmA@mail.gmail.com>
On Mon, Jul 14, 2014 at 1:38 PM, Or Gerlitz <or.gerlitz@gmail.com> wrote:
> On Mon, Jul 14, 2014 at 10:16 PM, Jerry Chu <hkchu@google.com> wrote:
>> On Mon, Jul 14, 2014 at 12:05 PM, Or Gerlitz <or.gerlitz@gmail.com> wrote:
>>> On Sun, Jul 13, 2014 at 5:46 PM, H.K. Jerry Chu <hkchu@google.com> wrote:
>>>> Fixed a bug that was introduced by my GRE-GRO patch
>>>> (bf5a755f5e9186406bbf50f4087100af5bd68e40 net-gre-gro: Add GRE
>>>> support to the GRO stack) that breaks the forwarding path
>>>> because various GSO related fields were not set. The bug 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.
>
>>> Anything different in this version vs. the one you posted earlier on
>>> February or this is a plain re-post?
>
>> I simply moved the patch against the latest net-next and resolved some small
>> conflict so yes it's pretty much the same.
>
> OK, got it.
>
>> Also I don't see the subsequent
>> discussion on skb->encapsulation affects the validity of this patch so
>> i'm resubmitting it. Also the patch has been confirmed to address the problem
>> Wolfgang reported last week. Feel free to test against the configuration (VXLAN?)
>> you had some question about earlier.
>
> Well, re-reading that thread, we were not very decisive there... my
> comment of setting the inner network header twice in inet_gro_complete
> doesn't apply only to vxlan but to other tunneling protocols.
Understood, but my reply about it applying to the inner most hdr in the end
is not limited to vxlan either.
> Also, if
> we really need (why do we? or explained it on the Feb thread) to set
> skb->encapsulation for the sake of TX in a protocol (GRE) gro
> complete, looks a bit fishy to me...
Why does it look fishy? When h/w support sLRO on tunneled pkts
driver will set that bit. So it seems very reasonable for the GRO stack
that supports tunneled pkts to set that bit too.
> but saying this I think brings us
> back to that incomplete discussion [1] sounds as this needs some
> plumbering... Still, this way or another I understand a regression was
> introduced here and should be fixed.
Yep. I thought we've made reasonable progress on the skb->encapsualtion
even though we can't close all the questions/issues (but we have a real
bug that needs to be fixed here).
Jerry
>
> Or.
>
> [1] http://marc.info/?t=139353642700003&r=1&w=2
next prev parent reply other threads:[~2014-07-14 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 14:46 [PATCH net-next] net-gre-gro: Fix a bug that breaks the forwarding path H.K. Jerry Chu
2014-07-14 19:05 ` Or Gerlitz
2014-07-14 19:16 ` Jerry Chu
2014-07-14 20:38 ` Or Gerlitz
2014-07-14 21:30 ` Jerry Chu [this message]
2014-07-15 14:06 ` Or Gerlitz
2014-07-15 17:17 ` Jerry Chu
2014-07-15 18:23 ` Or Gerlitz
2014-07-15 18:44 ` Tom Herbert
2014-07-16 12:12 ` Or Gerlitz
[not found] ` <CAJZOPZLqqBad5p_TH2gvHsWOgrNWdwUz0A4x-20mr2Jw-Ev=8Q@mail.gmail.com>
2014-07-15 20:22 ` Jerry Chu
2014-07-16 12:15 ` Or Gerlitz
2014-07-14 22:05 ` David Miller
2014-07-14 22:18 ` Jerry Chu
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='CAPshTCiKnKx_P=JLQcgjS36rWmCtSS43XYNJHeif9Z9yP8C36Q@mail.gmail.com' \
--to=hkchu@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux@stwm.de \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=or.gerlitz@gmail.com \
--cc=therbert@google.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).