From: Eric Dumazet <edumazet@kernel.org>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, edumazet@google.com,
Eric Dumazet <edumazet@kernel.org>
Subject: [PATCH net 0/2] ipv4: fix IP ID reuse for GSO packets
Date: Tue, 29 Sep 2026 13:12:45 +0000 [thread overview]
Message-ID: <20260929131247.401104-1-edumazet@kernel.org> (raw)
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.
- Patch 2 makes __ip_make_skb() reserve one IP ID per segment for
UDP GSO packets, instead of a single one.
Both issues were found by code inspection.
Eric Dumazet (2):
ipv4: fix IP ID reuse in ip_select_ident_segs()
ipv4: reserve one IP ID per segment for UDP GSO packets
include/net/ip.h | 2 +-
net/ipv4/ip_output.c | 15 ++++++++++++++-
2 files changed, 15 insertions(+), 2 deletions(-)
--
2.56.0.rc1.315.gc6ed9934b7-goog
next reply other threads:[~2026-09-29 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 13:12 Eric Dumazet [this message]
2026-09-29 13:12 ` [PATCH net 1/2] ipv4: fix IP ID reuse in ip_select_ident_segs() Eric Dumazet
2026-09-30 6:20 ` Jiayuan Chen
2026-09-30 12:30 ` David Ahern
2026-09-29 13:12 ` [PATCH net 2/2] ipv4: reserve one IP ID per segment for UDP GSO packets Eric Dumazet
2026-09-30 6:18 ` Jiayuan Chen
2026-09-30 12:28 ` David Ahern
2026-09-30 12:58 ` Eric Dumazet
2026-09-30 13:50 ` David Ahern
2026-09-30 14:24 ` 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=20260929131247.401104-1-edumazet@kernel.org \
--to=edumazet@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.