linux-kernel - Re: [PATCH 1/3] net: phy: Check phy

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: <20180607181230.GF25513@lunn.ch>
Date:   Thu, 7 Jun 2018 20:12:30 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Brandon Maier <brandon.maier@...kwellcollins.com>
Cc:     netdev@...r.kernel.org, f.fainelli@...il.com, davem@...emloft.net,
        michal.simek@...inx.com,
        Clayton Shotwell <clayton.shotwell@...kwellcollins.com>,
        Kristopher Cory <kristopher.cory@...kwellcollins.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] net: phy: Check phy_driver ready before accessing

> Agreed. Another thing that looks suspicious to me is the driver
> overrides the private data of the device it's attaching too, in the
> `priv->phy_dev->priv = priv` bit. Seems like that could cause all
> sorts of driver corruption problems.

Ah, yes. That is very broken. Many PHYs will just explode sometime
later, since they use phdev->priv.

> But fixing that is going to require more drastic changes to how this
> driver works. So it'd be worth applying this patch in the mean time.

Patches welcome.

	Andrew