From: Donald Hunter <donald.hunter@gmail.com>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
David Ahern <dsahern@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/3] netlink: specs: fou: change local-v6/peer-v6 check
Date: Wed, 03 Sep 2025 09:32:34 +0100 [thread overview]
Message-ID: <m25xe00wd9.fsf@gmail.com> (raw)
In-Reply-To: <20250902154640.759815-2-ast@fiberby.net>
Asbjørn Sloth Tønnesen <ast@fiberby.net> writes:
> While updating the binary min-len implementation, I noticed that
> the only user, should AFAICT be using exact-len instead.
>
> In net/ipv4/fou_core.c FOU_ATTR_LOCAL_V6 and FOU_ATTR_PEER_V6
> are only used for singular IPv6 addresses, and there are AFAICT
> no known implementations trying to send more, it therefore
> appears safe to change it to an exact-len policy.
>
> This patch therefore changes the local-v6/peer-v6 attributes to
> use an exact-len check, instead of a min-len check.
>
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
next prev parent reply other threads:[~2025-09-03 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 15:46 [PATCH net-next v2 0/3] tools: ynl-gen: misc changes Asbjørn Sloth Tønnesen
2025-09-02 15:46 ` [PATCH net-next v2 1/3] netlink: specs: fou: change local-v6/peer-v6 check Asbjørn Sloth Tønnesen
2025-09-03 8:32 ` Donald Hunter [this message]
2025-09-02 15:46 ` [PATCH net-next v2 2/3] tools: ynl-gen: use macro for binary min-len check Asbjørn Sloth Tønnesen
2025-09-03 8:52 ` Donald Hunter
2025-09-02 15:46 ` [PATCH net-next v2 3/3] genetlink: fix typo in comment Asbjørn Sloth Tønnesen
2025-09-03 8:52 ` Donald Hunter
2025-09-03 22:20 ` [PATCH net-next v2 0/3] tools: ynl-gen: misc changes patchwork-bot+netdevbpf
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=m25xe00wd9.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=ast@fiberby.net \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@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 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).