netdev - Re: [PATCH v2 net] r8169: fix LED-related deadlock on module removal

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: 
 <171274262824.13361.13300515768136013023.git-patchwork-notify@kernel.org>
Date: Wed, 10 Apr 2024 09:50:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Heiner Kallweit <hkallweit1@...il.com>
Cc: edumazet@...gle.com, pabeni@...hat.com, kuba@...nel.org,
 davem@...emloft.net, nic_swsd@...ltek.com, lukas@...ner.de,
 netdev@...r.kernel.org, andrew@...n.ch
Subject: Re: [PATCH v2 net] r8169: fix LED-related deadlock on module removal

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:

On Mon, 8 Apr 2024 20:47:40 +0200 you wrote:
> Binding devm_led_classdev_register() to the netdev is problematic
> because on module removal we get a RTNL-related deadlock. Fix this
> by avoiding the device-managed LED functions.
> 
> Note: We can safely call led_classdev_unregister() for a LED even
> if registering it failed, because led_classdev_unregister() detects
> this and is a no-op in this case.
> 
> [...]

Here is the summary with links:
  - [v2,net] r8169: fix LED-related deadlock on module removal
    https://git.kernel.org/netdev/net/c/19fa4f2a85d7

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