From: David Ahern <dsahern@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v2 0/7] net: deduplicate cookie logic
Date: Wed, 12 Feb 2025 13:11:22 -0700 [thread overview]
Message-ID: <5281a36d-e46d-44d0-80ac-9a65d8201863@kernel.org> (raw)
In-Reply-To: <20250212021142.1497449-1-willemdebruijn.kernel@gmail.com>
On 2/11/25 7:09 PM, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> Reuse standard sk, ip and ipv6 cookie init handlers where possible.
>
> Avoid repeated open coding of the same logic.
> Harmonize feature sets across protocols.
> Make IPv4 and IPv6 logic more alike.
> Simplify adding future new fields with a single init point.
>
> v1->v2:
> - limit INET_DSCP_MASK to routing
> - remove no longer used local variable (fix build warning)
>
> Willem de Bruijn (7):
> tcp: only initialize sockcm tsflags field
> net: initialize mark in sockcm_init
> ipv4: initialize inet socket cookies with sockcm_init
> ipv4: remove get_rttos
> icmp: reflect tos through ip cookie rather than updating inet_sk
> ipv6: replace ipcm6_init calls with ipcm6_init_sk
> ipv6: initialize inet socket cookies with sockcm_init
>
> include/net/ip.h | 16 +++++-----------
> include/net/ipv6.h | 11 ++---------
> include/net/sock.h | 1 +
> net/can/raw.c | 2 +-
> net/ipv4/icmp.c | 6 ++----
> net/ipv4/ping.c | 6 +++---
> net/ipv4/raw.c | 6 +++---
> net/ipv4/tcp.c | 2 +-
> net/ipv4/udp.c | 6 +++---
> net/ipv6/ping.c | 3 ---
> net/ipv6/raw.c | 15 +++------------
> net/ipv6/udp.c | 10 +---------
> net/l2tp/l2tp_ip6.c | 8 +-------
> net/packet/af_packet.c | 9 ++++-----
> 14 files changed, 30 insertions(+), 71 deletions(-)
>
LGTM. For the set
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2025-02-12 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 2:09 [PATCH net-next v2 0/7] net: deduplicate cookie logic Willem de Bruijn
2025-02-12 2:09 ` [PATCH net-next v2 1/7] tcp: only initialize sockcm tsflags field Willem de Bruijn
2025-02-12 2:09 ` [PATCH net-next v2 2/7] net: initialize mark in sockcm_init Willem de Bruijn
2025-02-13 14:48 ` Paolo Abeni
2025-02-13 15:35 ` Willem de Bruijn
2025-02-13 18:12 ` Paolo Abeni
2025-02-12 2:09 ` [PATCH net-next v2 3/7] ipv4: initialize inet socket cookies with sockcm_init Willem de Bruijn
2025-02-12 2:09 ` [PATCH net-next v2 4/7] ipv4: remove get_rttos Willem de Bruijn
2025-02-13 15:10 ` Paolo Abeni
2025-02-13 16:23 ` Willem de Bruijn
2025-02-13 16:29 ` Willem de Bruijn
2025-02-13 17:23 ` Paolo Abeni
2025-02-12 2:09 ` [PATCH net-next v2 5/7] icmp: reflect tos through ip cookie rather than updating inet_sk Willem de Bruijn
2025-02-12 2:09 ` [PATCH net-next v2 6/7] ipv6: replace ipcm6_init calls with ipcm6_init_sk Willem de Bruijn
2025-02-12 2:09 ` [PATCH net-next v2 7/7] ipv6: initialize inet socket cookies with sockcm_init Willem de Bruijn
2025-02-12 20:11 ` David Ahern [this message]
2025-02-14 21:06 ` [PATCH net-next v2 0/7] net: deduplicate cookie logic Jakub Kicinski
2025-02-14 22:34 ` Willem de Bruijn
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=5281a36d-e46d-44d0-80ac-9a65d8201863@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).