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: Thu, 23 Sep 2021 22:44:48 +0300 From: Vladimir Oltean <olteanv@...il.com> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: Saravana Kannan <saravanak@...gle.com>, "Rafael J. Wysocki" <rafael@...nel.org>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Len Brown <lenb@...nel.org>, Geert Uytterhoeven <geert@...ux-m68k.org>, kernel-team@...roid.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: [PATCH v3 0/3] fw_devlink bug fixes On Thu, Sep 23, 2021 at 07:30:04PM +0200, Greg Kroah-Hartman wrote: > It fixes the real problem where drivers were making the wrong assumption > that if they registered a device, it would be instantly bound to a > driver. Drivers that did this were getting lucky, as this was never a > guarantee of the driver core (think about if you enabled async > probing, and the mess with the bus specific locks that should be > preventing much of this) Since commit d173a137c5bd ("driver-core: enable drivers to opt-out of async probe") it is possible to opt out of async probing, and PHY drivers do opt out of it, at the time of writing.
Powered by blists - more mailing lists