From: sashiko-bot@kernel.org
To: "Eric Dumazet" <edumazet@kernel.org>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net v2 3/3] selftests: net: tun: test outer protocol of UDP tunnel GSO packets
Date: Thu, 05 Nov 2026 05:01:53 +0000 [thread overview]
Message-ID: <sashiko-outbox-198575@kernel.org> (raw)
In-Reply-To: <20261104050131.629967-4-edumazet@kernel.org>
> Add tests writing single 4in4 Geneve GSO frames to tun devices with
> UDP tunnel offloads enabled.
>
> tun_vnet_udptnl_proto uses a tap device:
>
> - outer_proto_ok: an outer IPv4 header, with or without an 802.1Q tag,
> is accepted.
> - outer_proto_bad: an outer ethertype that does not match the declared
> tunnel type (IPv6 on an IPv4 tunnel, or NSH, with or without a VLAN
> tag) is rejected with EINVAL.
>
> tun_vnet_udptnl_proto_l3 uses an IFF_TUN device with a tun_pi header,
> so skb->protocol comes from userspace and there is no Ethernet header.
> The outer IPv4 header carries options, as virtio_net_hdr_tnl_to_skb()
> expects room for an Ethernet header before the outer transport header.
>
> - outer_proto_ok: tun_pi and the frame agree on IPv4, accepted.
> - outer_proto_bad: tun_pi claims IPv6, or the IP version of the frame
> is not 4 while tun_pi claims IPv4: rejected with EINVAL.
>
> Without the first patch of this series, both outer_proto_bad tests fail
> because the kernel accepts the frames.
>
> Signed-off-by: Eric Dumazet <edumazet@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104050131.629967-1-edumazet@kernel.org?part=3
next prev parent reply other threads:[~2026-11-05 5:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 5:01 [PATCH net v2 0/3] net: virtio: validate outer protocol of UDP tunnel GSO packets Eric Dumazet
2026-11-04 5:01 ` [PATCH net v2 1/3] " Eric Dumazet
2026-11-04 15:32 ` Willem de Bruijn
2026-11-04 15:36 ` Michael S. Tsirkin
2026-11-05 5:01 ` sashiko-bot
2026-11-05 10:08 ` netdev-bot+sashiko
2026-11-05 11:52 ` Eric Dumazet
2026-11-04 5:01 ` [PATCH net v2 2/3] selftests: net: tuntap: fix UDP checksum length in build_udp_packet_csum() Eric Dumazet
2026-11-05 5:01 ` sashiko-bot
2026-11-04 5:01 ` [PATCH net v2 3/3] selftests: net: tun: test outer protocol of UDP tunnel GSO packets Eric Dumazet
2026-11-04 15:36 ` Willem de Bruijn
2026-11-05 5:01 ` sashiko-bot [this message]
2026-11-05 10:08 ` netdev-bot+sashiko
2026-11-05 11:54 ` Eric Dumazet
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=sashiko-outbox-198575@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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