MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Davide Caratti <dcaratti@redhat.com>
Cc: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH net-next v2] tools: ynl-gen: use big-endian netlink attribute types
Date: Thu, 17 Oct 2024 12:48:54 +0200	[thread overview]
Message-ID: <79bc45a2-452f-447d-96b3-187c45e15d26@kernel.org> (raw)
In-Reply-To: <20241017094704.3222173-1-ast@fiberby.net>

Hi Davide,

On 17/10/2024 11:47, 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().

This modification looks good to me, but just in case, do you mind having
a quick look, and eventually send your Acked-by, please? :)

(...)

> diff --git a/net/mptcp/mptcp_pm_gen.c b/net/mptcp/mptcp_pm_gen.c
> index c30a2a90a192..5a6b2b4510d3 100644
> --- a/net/mptcp/mptcp_pm_gen.c
> +++ b/net/mptcp/mptcp_pm_gen.c
> @@ -14,7 +14,7 @@
>  const struct nla_policy mptcp_pm_address_nl_policy[MPTCP_PM_ADDR_ATTR_IF_IDX + 1] = {
>  	[MPTCP_PM_ADDR_ATTR_FAMILY] = { .type = NLA_U16, },
>  	[MPTCP_PM_ADDR_ATTR_ID] = { .type = NLA_U8, },
> -	[MPTCP_PM_ADDR_ATTR_ADDR4] = { .type = NLA_U32, },
> +	[MPTCP_PM_ADDR_ATTR_ADDR4] = { .type = NLA_BE32, },
>  	[MPTCP_PM_ADDR_ATTR_ADDR6] = NLA_POLICY_EXACT_LEN(16),
>  	[MPTCP_PM_ADDR_ATTR_PORT] = { .type = NLA_U16, },
>  	[MPTCP_PM_ADDR_ATTR_FLAGS] = { .type = NLA_U32, },

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2024-10-17 10:48 UTC|newest]

Thread overview: 5+ 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-17 10:48 ` Matthieu Baerts [this message]
2024-10-17 11:02 ` MPTCP CI
2024-10-18 11:46 ` Simon Horman
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=79bc45a2-452f-447d-96b3-187c45e15d26@kernel.org \
    --to=matttbe@kernel.org \
    --cc=dcaratti@redhat.com \
    --cc=mptcp@lists.linux.dev \
    /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