From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, dsahern@kernel.org, idosch@nvidia.com,
netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH v2 net 0/2] ipv4: fix IP ID reuse for GSO packets
Date: Mon, 05 Oct 2026 22:10:16 +0000 [thread overview]
Message-ID: <179123821677.1914306.18110720981322113793.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930144018.1174068-1-edumazet@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Sep 2026 14:40:16 +0000 you wrote:
> This series fixes two cases where IPv4 GSO packets can reuse the IP IDs
> of previous packets:
>
> - Patch 1 fixes ip_select_ident_segs() for non-TCP sockets, which uses
> the first IP ID of the next packet since commit f866fbc842de
> ("ipv4: fix data-races around inet->inet_id"). SCTP GSO is affected.
>
> [...]
Here is the summary with links:
- [v2,net,1/2] ipv4: fix IP ID reuse in ip_select_ident_segs()
https://git.kernel.org/netdev/net-next/c/fe7ca0c13f7d
- [v2,net,2/2] ipv4: reserve one IP ID per segment for UDP GSO packets
https://git.kernel.org/netdev/net-next/c/852c08d6a991
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-10-05 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:40 [PATCH v2 net 0/2] ipv4: fix IP ID reuse for GSO packets Eric Dumazet
2026-09-30 14:40 ` [PATCH v2 net 1/2] ipv4: fix IP ID reuse in ip_select_ident_segs() Eric Dumazet
2026-09-30 15:11 ` Willem de Bruijn
2026-09-30 14:40 ` [PATCH v2 net 2/2] ipv4: reserve one IP ID per segment for UDP GSO packets Eric Dumazet
2026-09-30 15:12 ` Willem de Bruijn
2026-10-05 22:10 ` 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=179123821677.1914306.18110720981322113793.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.