netdev - Re: [PATCH net] net: phy: add workaround for issue where PHY driver doesn't bind to the device

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: <20181127.150109.131418314942116531.davem@davemloft.net>
Date:   Tue, 27 Nov 2018 15:01:09 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     hkallweit1@...il.com
Cc:     andrew@...n.ch, f.fainelli@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH net] net: phy: add workaround for issue where PHY
 driver doesn't bind to the device

From: Heiner Kallweit <hkallweit1@...il.com>
Date: Fri, 23 Nov 2018 19:41:29 +0100

> After switching the r8169 driver to use phylib some user reported that
> their network is broken. This was caused by the genphy PHY driver being
> used instead of the dedicated PHY driver for the RTL8211B. Users
> reported that loading the Realtek PHY driver module upfront fixes the
> issue. See also this mail thread:
> https://marc.info/?t=154279781800003&r=1&w=2
> The issue is quite weird and the root cause seems to be somewhere in
> the base driver core. The patch works around the issue and may be
> removed once the actual issue is fixed.
> 
> The Fixes tag refers to the first reported occurrence of the issue.
> The issue itself may have been existing much longer and it may affect
> users of other network chips as well. Users typically will recognize
> this issue only if their PHY stops working when being used with the
> genphy driver.
> 
> Fixes: f1e911d5d0df ("r8169: add basic phylib support")
> Signed-off-by: Heiner Kallweit <hkallweit1@...il.com>

Applied and queued up for -stable.