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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 30 Apr 2022 17:52:56 +0200 From: Andrew Lunn <andrew@...n.ch> To: Peter Geis <pgwipeout@...il.com> Cc: "Russell King (Oracle)" <linux@...linux.org.uk>, Heiner Kallweit <hkallweit1@...il.com>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>, Linux Kernel Network Developers <netdev@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v1] net: phy: fix motorcomm module automatic loading > Good Morning, > > After testing various configurations I found what is actually > happening here. When libphy is built in but the phy drivers are > modules and not available in the initrd, the generic phy driver binds > here. This allows the phy to come up but it is not functional. What MAC are you using? Why is you interface being brought up by the initramfs? Are you using NFS root from within the initramfs? What normally happens is that the kernel loads, maybe with the MAC driver and phylib loading, as part of the initramfs. The other modules in the initramfs allow the root filesystem to be found, mounted, and pivoted into it. The MAC driver is then brought up by the initscripts, which causes phylib to request the needed PHY driver modules, it loads and all is good. If you are using NFS root, then the load of the PHY driver happens earlier, inside the initramfs. If this is you situation, maybe the correct fix is to teach the initramfs tools to include the PHY drivers when NFS root is being used? Andrew
Powered by blists - more mailing lists