netdev - Re: [PATCH v2] leds: trigger: netdev: fix RTNL handling to prevent potential deadlock

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: <20231205192109.7c7fa56b@kernel.org>
Date: Tue, 5 Dec 2023 19:21:09 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>
Cc: Heiner Kallweit <hkallweit1@...il.com>, Christian Marangi
 <ansuelsmth@...il.com>, Andrew Lunn <andrew@...n.ch>,
 "linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
 "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Simon Horman
 <horms@...nel.org>
Subject: Re: [PATCH v2] leds: trigger: netdev: fix RTNL handling to prevent
 potential deadlock

On Mon, 4 Dec 2023 14:48:08 -0800 Jakub Kicinski wrote:
> On Fri, 1 Dec 2023 11:23:22 +0100 Heiner Kallweit wrote:
> > When working on LED support for r8169 I got the following lockdep
> > warning. Easiest way to prevent this scenario seems to be to take
> > the RTNL lock before the trigger_data lock in set_device_name().  
> 
> Pavel/Lee, would you like to handle this patch?
> Or should we ship it to Linus on Thu?

Better safe than step on someone's toes, so I'll drop this version
from the netdev PW.