netdev - Re: [PATCH] net: phy: don't issue a module request if a driver is available

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: <cff14918-0143-4309-9317-675c18ad3a8f@lunn.ch>
Date: Fri, 3 Jan 2025 15:12:14 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Niklas Cassel <cassel@...nel.org>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
	Francesco Valla <francesco@...la.it>,
	Andrew Lunn <andrew+netdev@...n.ch>,
	Heiner Kallweit <hkallweit1@...il.com>, netdev@...r.kernel.org,
	Anand Moon <linux.amoon@...il.com>
Subject: Re: [PATCH] net: phy: don't issue a module request if a driver is
 available

> FWIW, the patch in $subject does make the splat go away for me.
> (I have the PHY driver built as built-in).
> 
> The patch in $subject does "Add a list of registered drivers and check
> if one is already available before resorting to call request_module();
> in this way, if the PHY driver is already there, the MDIO bus can perform
> the async probe."

Lets take a step backwards.

How in general should module loading work with async probe? Lets
understand that first.

Then we can think about what is special about PHYs, and how we can fit
into the existing framework.

	Andrew