linux-kernel - Re: [PATCH] net: macb: Add support for phy-handle binding

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]

Date:	Wed, 17 Feb 2016 12:14:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	nathan@...hanrossi.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	nicolas.ferre@...el.com
Subject: Re: [PATCH] net: macb: Add support for phy-handle binding

From: Nathan Rossi <nathan@...hanrossi.com>
Date: Sun, 14 Feb 2016 02:02:48 +1000

> This patch adds support for the 'phy-handle' binding which allows for a
> system to specifically select a phy which can be attached via any MDIO
> bus available in the system.
> 
> Signed-off-by: Nathan Rossi <nathan@...hanrossi.com>
> Cc: Nicolas Ferre <nicolas.ferre@...el.com>

I don't see how this can be backwards compatible at all.

In my opinion we are way too loose about handling things like this.

Existing chips that happened to have an OF node but lack a phy-handle
property are going to be broken by that change.

I know you are now going to bombard me with all kinds of reasons why
this won't happen.

Don't bother, I'm simply not interested.

All of these special cases we use (all the DT bindings are in text
files in the kernel sources, we control all of the bootloaders, etc.)
is the most shaky foundation I've ever seen upon which to erect a
stable device probing mechanism.

I'm not applying this patch until you add an error handling path from
the of_phy_connect() call that will do the existing PHY probing sequence
by hand using phy_find_first().