netdev - Re: [PATCH 00/21] NET: use unique MDIO bus names

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: <20120110.163524.906859005643528607.davem@davemloft.net>
Date:	Tue, 10 Jan 2012 16:35:24 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	florian@...nwrt.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 00/21] NET: use unique MDIO bus names

From: Florian Fainelli <florian@...nwrt.org>
Date: Tue, 10 Jan 2012 10:59:06 +0100

> While troubleshooting an issue with an user of the RDC r6040 driver
> having compiled support for the fixed MDIO bus, I noticed that quite
> some network drivers will have a MDIO bus named "0" most of the time.
> 
> Some network drivers already try to provide an unique MDIO bus name
> using their PCI slot and function, this is okay.
> 
> Some other network drivers will format the name using their platform_device
> id, which will usually result in a collision with the fixed MDIO bus
> name ("0"), these drivers are fixed to use the following pattern instead:
> 
> <platform_device name>-<platform device id> which is unique
> 
> Finally the MDIO bus drivers themselves are patched to use an unique name
> as well.
> 
> There is a potential to break user-space applications assuming there is a
> specific MDIO bus named "0", "1" or other non-explanatory names like this.
> 
> Note that I compile tested most of the drivers on x86 and MIPS, ARM and Blackfin
> drivers have not been compile tested.

All applied, thanks Florian.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html