[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250310115845.17a04100@kmaincent-XPS-13-7390>
Date: Mon, 10 Mar 2025 11:58:45 +0100
From: Kory Maincent <kory.maincent@...tlin.com>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: davem@...emloft.net, Andrew Lunn <andrew@...n.ch>, Jakub Kicinski
<kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Heiner Kallweit <hkallweit1@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
thomas.petazzoni@...tlin.com, linux-arm-kernel@...ts.infradead.org,
Christophe Leroy <christophe.leroy@...roup.eu>, Herve Codina
<herve.codina@...tlin.com>, Florian Fainelli <f.fainelli@...il.com>,
Russell King <linux@...linux.org.uk>, Vladimir Oltean
<vladimir.oltean@....com>, Oleksij Rempel <o.rempel@...gutronix.de>, Simon
Horman <horms@...nel.org>, Romain Gantois <romain.gantois@...tlin.com>,
Piergiorgio Beruto <piergiorgio.beruto@...il.com>, Stanislav Fomichev
<sdf@...ichev.me>
Subject: Re: [PATCH net-next v2 1/7] net: ethtool: netlink: Allow
per-netdevice DUMP operations
On Sat, 8 Mar 2025 16:54:33 +0100
Maxime Chevallier <maxime.chevallier@...tlin.com> wrote:
> We have a number of netlink commands in the ethnl family that may have
> multiple objects to dump even for a single net_device, including :
>
> - PLCA, PSE-PD, phy: one message per PHY device
> - tsinfo: one message per timestamp source (netdev + phys)
> - rss: One per RSS context
>
> To get this behaviour, these netlink commands need to roll a custom
> ->dumpit().
>
> To prepare making per-netdev DUMP more generic in ethnl, introduce a
> member in the ethnl ops to indicate if a given command may allow
> pernetdev DUMPs (also referred to as filtered DUMPs).
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@...tlin.com>
> ---
> V2: - Rebase
> - Fix kdoc
> - Fix bissectabilitu by using the right function names
>
> net/ethtool/netlink.c | 45 ++++++++++++++++++++++++++++---------------
> net/ethtool/netlink.h | 2 ++
> 2 files changed, 31 insertions(+), 16 deletions(-)
>
> diff --git a/net/ethtool/netlink.c b/net/ethtool/netlink.c
> index 70834947f474..11e4122b7707 100644
> --- a/net/ethtool/netlink.c
> +++ b/net/ethtool/netlink.c
> @@ -586,21 +586,34 @@ static int ethnl_default_dumpit(struct sk_buff *skb,
> int ret = 0;
>
> rcu_read_lock();
> - for_each_netdev_dump(net, dev, ctx->pos_ifindex) {
> - dev_hold(dev);
> + if (ctx->req_info->dev) {
> + dev = ctx->req_info->dev;
> rcu_read_unlock();
> -
> - ret = ethnl_default_dump_one(skb, dev, ctx,
> genl_info_dump(cb)); -
> + /* Filtered DUMP request targeted to a single netdev. We
> already
> + * hold a ref to the netdev from ->start()
> + */
> + ret = ethnl_default_dump_one(skb, dev, ctx,
> + genl_info_dump(cb));
> rcu_read_lock();
> - dev_put(dev);
> -
> - if (ret < 0 && ret != -EOPNOTSUPP) {
> - if (likely(skb->len))
> - ret = skb->len;
> - break;
You are not checking -EOPNOTSUPP, so you can return this error in the
ctx->req_info->dev condition. I am not sure about the policy but do we want to
report the EOPNOTSUPP error in the dump command instead of simply returning
nothing.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
Powered by blists - more mailing lists