From: Simon Horman <horms@kernel.org>
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>,
David Ahern <dsahern@kernel.org>,
Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] tools: ynl-gen: use big-endian netlink attribute types
Date: Fri, 18 Oct 2024 12:46:46 +0100 [thread overview]
Message-ID: <20241018114646.GH1697@kernel.org> (raw)
In-Reply-To: <20241017094704.3222173-1-ast@fiberby.net>
On Thu, Oct 17, 2024 at 09:47:02AM +0000, Asbjørn Sloth Tønnesen wrote:
> Change ynl-gen-c.py to use NLA_BE16 and NLA_BE32 types to represent
> big-endian u16 and u32 ynl types.
>
> Doing this enables those attributes to have range checks applied, as
> the validator will then convert to host endianness prior to validation.
>
> The autogenerated kernel/uapi code have been regenerated by running:
> ./tools/net/ynl/ynl-regen.sh -f
>
> This changes the policy types of the following attributes:
>
> FOU_ATTR_PORT (NLA_U16 -> NLA_BE16)
> FOU_ATTR_PEER_PORT (NLA_U16 -> NLA_BE16)
> These two are used with nla_get_be16/nla_put_be16().
>
> MPTCP_PM_ADDR_ATTR_ADDR4 (NLA_U32 -> NLA_BE32)
> This one is used with nla_get_in_addr/nla_put_in_addr(),
> which uses nla_get_be32/nla_put_be32().
>
> IOWs the generated changes are AFAICT aligned with their implementations.
>
> The generated userspace code remains identical, and have been verified
> by comparing the output generated by the following command:
> make -C tools/net/ynl/generated
>
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
>
> ---
> Changelog:
>
> v2:
> - Re-implement to avoid adding a new Type attribute (Requested by Jakub).
>
> v1: https://lore.kernel.org/netdev/20240913085555.134788-1-ast@fiberby.net/
Thanks for addressing Jakub's review of v1.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-10-18 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 9:47 [PATCH net-next v2] tools: ynl-gen: use big-endian netlink attribute types Asbjørn Sloth Tønnesen
2024-10-18 11:46 ` Simon Horman [this message]
2024-10-22 13:40 ` 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=20241018114646.GH1697@kernel.org \
--to=horms@kernel.org \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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).