linux-kernel - Re: [PATCH net-next] net: phy: Don't register LEDs for genphy

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: 
 <175254120801.4044098.17800015732191157887.git-patchwork-notify@kernel.org>
Date: Tue, 15 Jul 2025 01:00:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Sean Anderson <sean.anderson@...ux.dev>
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
 netdev@...r.kernel.org, linux-kernel@...r.kernel.org, ansuelsmth@...il.com,
 f.fainelli@...il.com, pabeni@...hat.com, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org
Subject: Re: [PATCH net-next] net: phy: Don't register LEDs for genphy

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Thu, 10 Jul 2025 16:14:53 -0400 you wrote:
> If a PHY has no driver, the genphy driver is probed/removed directly in
> phy_attach/detach. If the PHY's ofnode has an "leds" subnode, then the
> LEDs will be (un)registered when probing/removing the genphy driver.
> This could occur if the leds are for a non-generic driver that isn't
> loaded for whatever reason. Synchronously removing the PHY device in
> phy_detach leads to the following deadlock:
> 
> [...]

Here is the summary with links:
  - [net-next] net: phy: Don't register LEDs for genphy
    https://git.kernel.org/netdev/net-next/c/a44312d58e78

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html