From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: ansuelsmth@gmail.com, pavel@ucw.cz, lee@kernel.org,
kuba@kernel.org, andrew@lunn.ch, linux-leds@vger.kernel.org,
netdev@vger.kernel.org, horms@kernel.org
Subject: Re: [PATCH v2] leds: trigger: netdev: fix RTNL handling to prevent potential deadlock
Date: Wed, 06 Dec 2023 16:19:02 +0000 [thread overview]
Message-ID: <170187954217.26038.13218917015861949443.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fb5c8294-2a10-4bf5-8f10-3d2b77d2757e@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 1 Dec 2023 11:23:22 +0100 you 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().
>
> ======================================================
> WARNING: possible circular locking dependency detected
> 6.7.0-rc2-next-20231124+ #2 Not tainted
>
> [...]
Here is the summary with links:
- [v2] leds: trigger: netdev: fix RTNL handling to prevent potential deadlock
https://git.kernel.org/netdev/net/c/fe2b1226656a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-06 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:23 [PATCH v2] leds: trigger: netdev: fix RTNL handling to prevent potential deadlock Heiner Kallweit
2023-12-01 21:57 ` Andrew Lunn
2023-12-04 22:48 ` Jakub Kicinski
2023-12-06 3:21 ` Jakub Kicinski
2023-12-06 13:32 ` Lee Jones
2023-12-06 16:19 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170187954217.26038.13218917015861949443.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).