netdev - Re: [PATCH net-next 4/4] net: dsa: remove phylink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y2T2fIb5SBRQbn8I@shell.armlinux.org.uk>
Date:   Fri, 4 Nov 2022 11:24:44 +0000
From:   "Russell King (Oracle)" <linux@...linux.org.uk>
To:     Vladimir Oltean <vladimir.oltean@....com>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     netdev@...r.kernel.org, Claudiu Manoil <claudiu.manoil@....com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        UNGLinuxDriver@...rochip.com,
        Heiner Kallweit <hkallweit1@...il.com>,
        Sean Anderson <sean.anderson@...o.com>,
        Colin Foster <colin.foster@...advantage.com>,
        Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 4/4] net: dsa: remove phylink_validate() method

On Tue, Nov 01, 2022 at 01:48:06PM +0200, Vladimir Oltean wrote:
> As of now, all DSA drivers use phylink_generic_validate() and there is
> no known use case remaining for a driver-specific link mode validation
> procedure. As such, remove this DSA operation and let phylink determine
> what is supported based on config->mac_capabilities, which all drivers
> provide.
> 
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
> ---
> Not all DSA drivers provide config->mac_capabilities, for example
> mv88e6060, lan9303 and vsc73xx don't. However, there have been users of
> those drivers on recent kernels and no one reported that they fail to
> establish a link, so I'm guessing that they work (somehow). But I must
> admit I don't understand why phylink_generic_validate() works when
> mac_capabilities=0. Anyway, these drivers did not provide a
> phylink_validate() method before and do not provide one now, so nothing
> changes for them.

There is one remaining issue that needs to be properly addressed,
which is the bcm_sf2 driver, which is basically buggy. The recent
kernel build bot reports reminded me of this.

I've tried talking to Florian about it, and didn't make much progress,
so I'm carrying a patch in my tree which at least makes what is
provided to phylink correct.

See
http://git.armlinux.org.uk/cgit/linux-arm.git/commit/?h=net-queue&id=63d77c1f9db167fd74994860a4a899df5c957aab
and all the FIXME comments in there.

This driver really needs to be fixed before we kill DSA's
phylink_validate method (although doing so doesn't change anything
in mainline, but will remove my reminder that bcm_sf2 is still
technically broken.)

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!