From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: davem@davemloft.net, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
linux-arm-kernel@lists.infradead.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Herve Codina <herve.codina@bootlin.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Simon Horman <horms@kernel.org>,
Romain Gantois <romain.gantois@bootlin.com>,
Piergiorgio Beruto <piergiorgio.beruto@gmail.com>
Subject: Re: [PATCH net] net: ethtool: Set the req_info->dev on DUMP requests for each dev
Date: Tue, 4 Mar 2025 17:15:15 +0100 [thread overview]
Message-ID: <20250304171515.297d15df@fedora.home> (raw)
In-Reply-To: <20250304170051.607097e9@kmaincent-XPS-13-7390>
Hi Köry,
On Tue, 4 Mar 2025 17:00:51 +0100
Kory Maincent <kory.maincent@bootlin.com> wrote:
> On Sun, 2 Mar 2025 17:21:36 +0100
> Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
>
> > There are a few netlink commands that rely on the req_info->dev field
> > being populated by ethnl in their ->prepare_data() and ->fill_reply().
> >
> > For a regular GET request, this will be set by ethnl_default_parse(),
> > which calls ethnl_parse_header_dev_get().
> >
> > In the case of a DUMP request, the ->prepare_data() and ->fill_reply()
> > callbacks will be called with the req_info->dev being NULL, which can
> > cause discrepancies in the behaviour between GET and DUMP results.
> >
> > The main impact is that ethnl_req_get_phydev() will not find any
> > phy_device, impacting :
> > - plca
> > - pse-pd
> > - stats
> >
> > Some other commands rely on req_info->dev, namely :
> > - coalesce in ->fill_reply to look for an irq_moder
> >
> > Although cable_test and tunnels also rely on req_info->dev being set,
> > that's not a problem for these commands as :
> > - cable_test doesn't support DUMP
> > - tunnels rolls its own ->dumpit (and sets dev in the req_info).
> > - phy also has its own ->dumpit
> >
> > All other commands use reply_data->dev (probably the correct way of
> > doing things) and aren't facing this issue.
> >
> > Simply set the dev in the req_info context when iterating to dump each
> > dev.
> >
> > Fixes: c15e065b46dc ("net: ethtool: Allow passing a phy index for some
> > commands") Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> > ---
> >
> > Fixes tag targets the phy-index commit, as it introduced a change in
> > behaviour for PLCA. From what I can tell, coalesce never correctly
> > detected irq_moder in DUMP requests.
> >
> > We could also consider fixing all individual commands that use
> > req_info->dev, however I'm not actually sure it's incorrect to do so,
> > feel free to correct me though.
> >
> > Maxime
> >
> > net/ethtool/netlink.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/net/ethtool/netlink.c b/net/ethtool/netlink.c
> > index b4c45207fa32..de967961d8fe 100644
> > --- a/net/ethtool/netlink.c
> > +++ b/net/ethtool/netlink.c
> > @@ -582,6 +582,7 @@ static int ethnl_default_dumpit(struct sk_buff *skb,
> > dev_hold(dev);
> > rcu_read_unlock();
> >
> > + ctx->req_info->dev = dev;
>
> I would rather put it in ethnl_default_dump_one() before
> ethnl_init_reply_data() call.
Ah yes true, that'll be more consistent with the other callpaths.
> With this change:
> Reviewed-by: Kory Maincent <kory.maincent@bootlin.com>
> Tested-by: Kory Maincent <kory.maincent@bootlin.com>
Thank you for testing, I'll respin.
Maxime
>
prev parent reply other threads:[~2025-03-04 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 16:21 [PATCH net] net: ethtool: Set the req_info->dev on DUMP requests for each dev Maxime Chevallier
2025-03-04 16:00 ` Kory Maincent
2025-03-04 16:15 ` Maxime Chevallier [this message]
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=20250304171515.297d15df@fedora.home \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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