From: patchwork-bot+netdevbpf@kernel.org
To: Julius Bairaktaris <julius@bairaktaris.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
dsahern@kernel.org, idosch@nvidia.com, willemb@google.com,
steffen.klassert@secunet.com, jiayuan.chen@linux.dev,
mfleming@cloudflare.com, almasrymina@google.com,
bigeasy@linutronix.de, richardbgobert@gmail.com,
ecree.xilinx@gmail.com, bsdhenrymartin@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5 0/4] ipmr: forward GSO multicast packets
Date: Thu, 19 Nov 2026 12:40:04 +0000 [thread overview]
Message-ID: <179509200478.3067204.6104899231005443965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1794151759.git.julius@bairaktaris.de>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 14 Nov 2026 19:26:56 +0100 you wrote:
> With fraglist GRO or UDP GRO forwarding on, a routed IPv4 multicast
> stream arrives as GSO packets. ipmr_prepare_xmit() drops every DF
> aggregate larger than the MTU, and ip_encap() sets no tunnel GSO state,
> so a GSO packet sent to a VIFF_TUNNEL vif is dropped during
> segmentation. With that state set, a fraglist aggregate reaches
> skb_segment_list() with tunnel headers, which can write before the head
> of a frag_list member; this also happens today when such a packet is
> routed into a tunnel device. Checking the segment length instead of
> skb->len relies on skb_gso_transport_seglen(), which counts the inner
> UDP header of an encapsulated UDP GSO packet 8 bytes short.
>
> [...]
Here is the summary with links:
- [net,v5,1/4] net: make room for the tunnel header in skb_segment_list()
https://git.kernel.org/netdev/net/c/abccf171fa8e
- [net,v5,2/4] net: gso: count the inner UDP header of encapsulated UDP GSO packets
(no matching commit)
- [net,v5,3/4] ipmr: set up GSO state for tunnel vifs
(no matching commit)
- [net,v5,4/4] ipmr: do not drop GSO packets that fit the MTU after segmentation
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-19 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 18:26 [PATCH net v5 0/4] ipmr: forward GSO multicast packets Julius Bairaktaris
2026-11-14 18:26 ` [PATCH net v5 1/4] net: make room for the tunnel header in skb_segment_list() Julius Bairaktaris
2026-11-19 12:26 ` Paolo Abeni
2026-11-14 18:26 ` [PATCH net v5 2/4] net: gso: count the inner UDP header of encapsulated UDP GSO packets Julius Bairaktaris
2026-11-16 0:47 ` netdev-bot+sashiko
2026-11-14 18:26 ` [PATCH net v5 3/4] ipmr: set up GSO state for tunnel vifs Julius Bairaktaris
2026-11-16 0:47 ` netdev-bot+sashiko
2026-11-14 18:27 ` [PATCH net v5 4/4] ipmr: do not drop GSO packets that fit the MTU after segmentation Julius Bairaktaris
2026-11-19 12:40 ` patchwork-bot+netdevbpf [this message]
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=179509200478.3067204.6104899231005443965.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=bigeasy@linutronix.de \
--cc=bsdhenrymartin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=julius@bairaktaris.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfleming@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=steffen.klassert@secunet.com \
--cc=willemb@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