From: Kory Maincent <kory.maincent@bootlin.com>
To: Nicolai Buchwitz <nb@tipi-net.de>, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] net: ethtool: reject an out of range hwtstamp provider index
Date: Fri, 25 Sep 2026 15:55:55 +0200 [thread overview]
Message-ID: <0ddf8280-0a66-4dbf-9195-1b90e97015c5@bootlin.com> (raw)
In-Reply-To: <20260925135237.3432266-2-nb@tipi-net.de>
On 9/25/26 15:52, Nicolai Buchwitz wrote:
> A provider index of 0xFFFFFFFF picks a provider on hardware that has
> none. phc_index is an int where -1 means no PHC, and the u32 from user
> space ends up as -1, so the two match.
>
> TSINFO_GET uses -1 for "no provider requested" and answers with the
> default provider instead of an error.
>
> Reject the value in the netlink policy, which covers every comparison
> site.
>
> Fixes: b9e3f7dc9ed9 ("net: ethtool: tsinfo: Enhance tsinfo to support several hwtstamp by net topology")
> Signed-off-by: Nicolai Buchwitz <nb@tipi-net.de>
> ---
> NLA_POLICY_MAX does not fit here, .max in struct nla_policy is s16.
>
> net/ethtool/ts.h | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/net/ethtool/ts.h b/net/ethtool/ts.h
> index d901a879a671..ab9805308353 100644
> --- a/net/ethtool/ts.h
> +++ b/net/ethtool/ts.h
> @@ -5,9 +5,15 @@
>
> #include "netlink.h"
>
> +/* phc_index is an int and -1 means no PHC, so keep the request non-negative */
> +static const struct netlink_range_validation ethnl_ts_prov_index_range = {
> + .max = INT_MAX,
> +};
> +
> static const struct nla_policy
> ethnl_ts_hwtst_prov_policy[ETHTOOL_A_TS_HWTSTAMP_PROVIDER_MAX + 1] = {
> - [ETHTOOL_A_TS_HWTSTAMP_PROVIDER_INDEX] = { .type = NLA_U32 },
> + [ETHTOOL_A_TS_HWTSTAMP_PROVIDER_INDEX] =
> + NLA_POLICY_FULL_RANGE(NLA_U32, ðnl_ts_prov_index_range),
> [ETHTOOL_A_TS_HWTSTAMP_PROVIDER_QUALIFIER] =
> NLA_POLICY_MAX(NLA_U32, HWTSTAMP_PROVIDER_QUALIFIER_CNT - 1)
> };
I think you can simply do this:
[ETHTOOL_A_TS_HWTSTAMP_PROVIDER_INDEX] =
NLA_POLICY_MAX(NLA_U32, INT_MAX),
> base-commit: 11536ee3d3e0b1bd35b6f3f8df55a6053eb0c71d
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-09-25 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260925135237.3432266-1-nb@tipi-net.de>
2026-09-25 13:52 ` Nicolai Buchwitz
2026-09-25 13:55 ` Kory Maincent [this message]
2026-09-25 14:07 ` Nicolai Buchwitz
2026-09-25 17:57 ` Kory Maincent
2026-09-25 13:52 ` [PATCH net v3 2/2] net: ethtool: let tsconfig reach a PHY-only timestamp provider Nicolai Buchwitz
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=0ddf8280-0a66-4dbf-9195-1b90e97015c5@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@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
all inboxes | Powered by JetHome®