[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201109200522.7a8fdecf@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Mon, 9 Nov 2020 20:05:22 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <alobakin@...me>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Miaohe Lin <linmiaohe@...wei.com>,
Martin Varghese <martin.varghese@...ia.com>,
Pravin B Shelar <pshelar@....org>,
Willem de Bruijn <willemb@...gle.com>,
Guillaume Nault <gnault@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
Florian Westphal <fw@...len.de>,
Steffen Klassert <steffen.klassert@...unet.com>,
Paolo Abeni <pabeni@...hat.com>,
Yadu Kishore <kyk.segfault@...il.com>,
Vladimir Oltean <vladimir.oltean@....com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 net-next] net: skb_vlan_untag(): don't reset
transport offset if set by GRO layer
On Mon, 09 Nov 2020 23:47:23 +0000 Alexander Lobakin wrote:
> Similar to commit fda55eca5a33f
> ("net: introduce skb_transport_header_was_set()"), avoid resetting
> transport offsets that were already set by GRO layer. This not only
> mirrors the behavior of __netif_receive_skb_core(), but also makes
> sense when it comes to UDP GSO fraglists forwarding: transport offset
> of such skbs is set only once by GRO receive callback and remains
> untouched and correct up to the xmitting driver in 1:1 case, but
> becomes junk after untagging in ingress VLAN case and breaks UDP
> GSO offload. This does not happen after this change, and all types
> of forwarding of UDP GSO fraglists work as expected.
>
> Since v1 [1]:
> - keep the code 1:1 with __netif_receive_skb_core() (Jakub).
>
> [1] https://lore.kernel.org/netdev/zYurwsZRN7BkqSoikWQLVqHyxz18h4LhHU4NFa2Vw@cp4-web-038.plabs.ch
>
> Signed-off-by: Alexander Lobakin <alobakin@...me>
Applied, thanks!
Powered by blists - more mailing lists