summaryrefslogtreecommitdiff
path: root/scripts/namespace.pl
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2017-03-07 20:33:31 +0300
committerDavid S. Miller <davem@davemloft.net>2017-03-10 00:19:52 +0300
commit294acf1c01bace5cea5d30b510504238bf5f7c25 (patch)
treeda8ec41e8eb09a842834979d8a1ee01197a38dd1 /scripts/namespace.pl
parent8aad6f14c09d78862fc04e47214d398add9bb8ce (diff)
downloadlinux-294acf1c01bace5cea5d30b510504238bf5f7c25.tar.xz
net/tunnel: set inner protocol in network gro hooks
The gso code of several tunnels type (gre and udp tunnels) takes for granted that the skb->inner_protocol is properly initialized and drops the packet elsewhere. On the forwarding path no one is initializing such field, so gro encapsulated packets are dropped on forward. Since commit 38720352412a ("gre: Use inner_proto to obtain inner header protocol"), this can be reproduced when the encapsulated packets use gre as the tunneling protocol. The issue happens also with vxlan and geneve tunnels since commit 8bce6d7d0d1e ("udp: Generalize skb_udp_segment"), if the forwarding host's ingress nic has h/w offload for such tunnel and a vxlan/geneve device is configured on top of it, regardless of the configured peer address and vni. To address the issue, this change initialize the inner_protocol field for encapsulated packets in both ipv4 and ipv6 gro complete callbacks. Fixes: 38720352412a ("gre: Use inner_proto to obtain inner header protocol") Fixes: 8bce6d7d0d1e ("udp: Generalize skb_udp_segment") Signed-off-by: Paolo Abeni <pabeni@redhat.com> Acked-by: Alexander Duyck <alexander.h.duyck@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/namespace.pl')
0 files changed, 0 insertions, 0 deletions