linux-kernel - Re: [PATCH v5] net: dsa: mt7530: fix impossible MDIO address and issue warning

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] [day] [month] [year] [list]

Message-ID: <20240708134328.hgwthqwcif5pjaig@skbuf>
Date: Mon, 8 Jul 2024 16:43:28 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: Daniel Golle <daniel@...rotopia.org>,
	Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>
Cc: Arınç ÜNAL <arinc.unal@...nc9.com>,
	DENG Qingfang <dqfext@...il.com>,
	Sean Wang <sean.wang@...iatek.com>, Andrew Lunn <andrew@...n.ch>,
	Florian Fainelli <f.fainelli@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Matthias Brugger <matthias.bgg@...il.com>,
	AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
	Landen Chao <Landen.Chao@...iatek.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v5] net: dsa: mt7530: fix impossible MDIO address and
 issue warning

On Mon, Jul 08, 2024 at 04:33:59PM +0300, Vladimir Oltean wrote:
> On Fri, Jul 05, 2024 at 11:48:40AM +0100, Daniel Golle wrote:
> > The MDIO address of the MT7530 and MT7531 switch ICs can be configured
> > using bootstrap pins. However, there are only 4 possible options for the
> > switch itself: 7, 15, 23 and 31. As in MediaTek's SDK the address of the
> > switch is wrongly stated in the device tree as 0 (while in reality it is
> > 31), warn the user about such broken device tree and make a good guess
> > what was actually intended.
> > 
> > This is necessary to not break compatibility with existing Device Trees
> > wrongly declaring the switch to be present at address 0 or 1, as with
> > commit 868ff5f4944a ("net: dsa: mt7530-mdio: read PHY address of switch
> > from device tree") the address in device tree will be taken into
> > account, while before it was hard-coded in the driver to 0x1f
> > independently of the value in Device Tree.
> > 
> > Fixes: b8f126a8d543 ("net-next: dsa: add dsa support for Mediatek MT7530 switch")
> > Signed-off-by: Daniel Golle <daniel@...rotopia.org>
> > Reviewed-by: Andrew Lunn <andrew@...n.ch>
> > Tested-by: Arınç ÜNAL <arinc.unal@...nc9.com>
> > Reviewed-by: Arınç ÜNAL <arinc.unal@...nc9.com>
> > ---
> 
> Despite having commented on v3, I am not going to leave a review tag on
> this patch. Its contents has nothing to do with DSA, so I have no
> technical objections of my own, plus little authority for an ack.
> It basically boils down to whether the phylib maintainers are okay with
> this use of mdio_device_remove() API from mdio_device drivers
> themselves.
> 
> I did have a technical concern in v3 about a race between the finishing
> of probe() and the call to mdio_device_remove(), which Daniel did not
> respond to, but I suspect that __device_driver_lock() from
> drivers/base/dd.c will serialize those.

Having that said, I noticed that this particular patch revision is not
entirely under their attention, so this is a heads up for them.
https://lore.kernel.org/netdev/f485d1d4f7b34cc2ebf3d60030d1c67b4016af3c.1720107535.git.daniel@makrotopia.org/