From: patchwork-bot+netdevbpf@kernel.org
To: Richard Gobert <richardbgobert@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com,
ecree.xilinx@gmail.com, willemdebruijn.kernel@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, corbet@lwn.net, saeedm@nvidia.com,
tariqt@nvidia.com, mbloch@nvidia.com, leon@kernel.org,
dsahern@kernel.org, ncardwell@google.com, kuniyu@google.com,
shuah@kernel.org, sdf@fomichev.me, aleksander.lobakin@intel.com,
florian.fainelli@broadcom.com, alexander.duyck@gmail.com,
linux-kernel@vger.kernel.org, linux-net-drivers@amd.com
Subject: Re: [PATCH net-next v8 0/5] net: gso: restore outer ip ids correctly
Date: Thu, 25 Sep 2025 10:50:12 +0000 [thread overview]
Message-ID: <175879741200.2924890.4123184469600808130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250923085908.4687-1-richardbgobert@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 23 Sep 2025 10:59:03 +0200 you wrote:
> GRO currently ignores outer IPv4 header IDs for encapsulated packets
> that have their don't-fragment flag set. GSO, however, always assumes
> that outer IP IDs are incrementing. This results in GSO mangling the
> outer IDs when they aren't incrementing. For example, GSO mangles the
> outer IDs of IPv6 packets that were converted to IPv4, which must
> have an ID of 0 according to RFC 6145, sect. 5.1.
>
> [...]
Here is the summary with links:
- [net-next,v8,1/5] net: gro: remove is_ipv6 from napi_gro_cb
https://git.kernel.org/netdev/net-next/c/25c550464acd
- [net-next,v8,2/5] net: gro: only merge packets with incrementing or fixed outer ids
https://git.kernel.org/netdev/net-next/c/21f7484220ac
- [net-next,v8,3/5] net: gso: restore ids of outer ip headers correctly
https://git.kernel.org/netdev/net-next/c/3271f19bf7b9
- [net-next,v8,4/5] net: gro: remove unnecessary df checks
https://git.kernel.org/netdev/net-next/c/f095a358faf2
- [net-next,v8,5/5] selftests/net: test ipip packets in gro.sh
https://git.kernel.org/netdev/net-next/c/5e9ff9378adc
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:[~2025-09-25 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 8:59 [PATCH net-next v8 0/5] net: gso: restore outer ip ids correctly Richard Gobert
2025-09-23 8:59 ` [PATCH net-next v8 1/5] net: gro: remove is_ipv6 from napi_gro_cb Richard Gobert
2025-09-23 8:59 ` [PATCH net-next v8 2/5] net: gro: only merge packets with incrementing or fixed outer ids Richard Gobert
2025-09-23 8:59 ` [PATCH net-next v8 3/5] net: gso: restore ids of outer ip headers correctly Richard Gobert
2025-09-23 21:26 ` Willem de Bruijn
2025-09-23 8:59 ` [PATCH net-next v8 4/5] net: gro: remove unnecessary df checks Richard Gobert
2025-09-23 8:59 ` [PATCH net-next v8 5/5] selftests/net: test ipip packets in gro.sh Richard Gobert
2025-09-25 10:50 ` 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=175879741200.2924890.4123184469600808130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=mbloch@nvidia.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=saeedm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=tariqt@nvidia.com \
--cc=willemdebruijn.kernel@gmail.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).