From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Simon Horman <horms@kernel.org>
Cc: christophe.leroy@csgroup.eu, thomas.petazzoni@bootlin.com,
andrew@lunn.ch, kuba@kernel.org, mwojtas@chromium.org,
kabel@kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, davem@davemloft.net, nicveronese@gmail.com,
hkallweit1@gmail.com, linux@armlinux.org.uk, edumazet@google.com,
dimitri.fedrau@liebherr.com, herve.codina@bootlin.com,
o.rempel@pengutronix.de, romain.gantois@bootlin.com,
netdev@vger.kernel.org, daniel@makrotopia.org,
vladimir.oltean@nxp.com, f.fainelli@gmail.com,
kory.maincent@bootlin.com
Subject: Re: [net-next,v3,01/11] net: phy: phy_port: Correctly recompute the port's linkmodes
Date: Tue, 3 Feb 2026 19:13:25 +0100 [thread overview]
Message-ID: <fd033a0e-4154-47e0-a15e-df92dd114f27@bootlin.com> (raw)
In-Reply-To: <20260203175813.2175230-1-horms@kernel.org>
Hi Simon
On 03/02/2026 18:58, Simon Horman wrote:
> This is an AI-generated review of your patch. The human sending this
> email has considered the AI review valid, or at least plausible.
>
> For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
> ---
> net: phy: phy_port: Correctly recompute the port's linkmodes
>
> This commit fixes phy_port_update_supported() to properly filter linkmodes
> instead of incorrectly or'ing medium-specific modes to the existing support.
> It moves the medium iteration inside a check for empty port->supported.
>
> Fixes: 589e934d2735 ("net: phy: Introduce PHY ports representation")
>
>> diff --git a/drivers/net/phy/phy_port.c b/drivers/net/phy/phy_port.c
>> --- a/drivers/net/phy/phy_port.c
>> +++ b/drivers/net/phy/phy_port.c
>
> [ ... ]
>
>> @@ -132,6 +126,19 @@ void phy_port_update_supported(struct phy_port *port)
>> port->pairs = max_t(int, port->pairs,
>> ethtool_linkmode_n_pairs(mode));
>>
>> + if (linkmode_empty(port->supported)) {
>> + for_each_set_bit(i, &port->mediums,
>> + __ETHTOOL_LINK_MEDIUM_LAST) {
>> + __ETHTOOL_DECLARE_LINK_MODE_MASK(med_supported) = {0};
>> +
>> + phy_caps_medium_get_supported(med_supported, i,
>> + port->pairs);
>> + linkmode_or(supported, supported, med_supported);
>> + }
>> +
>> + linkmode_and(port->supported, port->supported, supported);
Yeah :(
>> + }
>
> Jakub Kicinski raised a concern in v2 about the AND operation when
> port->supported starts empty. The v3 fix adds the
> 'if (linkmode_empty(port->supported))' check, but then still performs:
>
> linkmode_and(port->supported, port->supported, supported);
>
> inside that block. Since we just confirmed port->supported is empty,
> ANDing it with anything will always produce an empty result.
>
> Should this be linkmode_copy() or linkmode_or() instead of linkmode_and()
> when port->supported starts empty?
>
> Reference: https://lore.kernel.org/all/20260130040009.707764-1-kuba@kernel.org/
True, that's already addressed in V4 :)
Maxime
next prev parent reply other threads:[~2026-02-03 18:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 15:12 [PATCH net-next v3 00/11] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 01/11] net: phy: phy_port: Correctly recompute the port's linkmodes Maxime Chevallier
2026-02-03 17:58 ` [net-next,v3,01/11] " Simon Horman
2026-02-03 18:13 ` Maxime Chevallier [this message]
2026-02-01 15:12 ` [PATCH net-next v3 02/11] net: phy: phy_link_topology: Add a helper for opportunistic alloc Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 03/11] net: phy: phy_link_topology: Track ports in phy_link_topology Maxime Chevallier
2026-02-03 18:02 ` [net-next,v3,03/11] " Simon Horman
2026-02-03 18:11 ` Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 04/11] net: phylink: Register a phy_port for MAC-driven SFP busses Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 05/11] net: phy: Create SFP phy_port before registering usptream Maxime Chevallier
2026-02-03 17:52 ` Simon Horman
2026-02-03 18:09 ` Maxime Chevallier
2026-02-09 16:25 ` Simon Horman
2026-02-03 18:03 ` [net-next,v3,05/11] " Simon Horman
2026-02-03 18:12 ` Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 06/11] net: phy: Represent PHY-less SFP modules with phy_port Maxime Chevallier
2026-02-03 19:57 ` [net-next,v3,06/11] " Simon Horman
2026-02-01 15:12 ` [PATCH net-next v3 07/11] net: phylink: " Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 08/11] net: phy: phy_port: Store information about a MII port's vacant state Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 09/11] net: phy: phy_link_topology: Add a helper to retrieve ports Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 10/11] netlink: specs: Add ethernet port listing with ethtool Maxime Chevallier
2026-02-03 17:55 ` Simon Horman
2026-02-03 18:14 ` Maxime Chevallier
2026-02-01 15:12 ` [PATCH net-next v3 11/11] net: ethtool: Introduce ethtool command to list ports Maxime Chevallier
2026-02-02 7:56 ` [PATCH net-next v3 00/11] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
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=fd033a0e-4154-47e0-a15e-df92dd114f27@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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