From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
sdf@fomichev.me
Subject: Re: [PATCH net v2] bnxt_en: Fix lockdep warning during rmmod
Date: Tue, 19 Aug 2025 01:00:07 +0000 [thread overview]
Message-ID: <175556520776.2966773.2798007329883348467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250816183850.4125033-1-michael.chan@broadcom.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 16 Aug 2025 11:38:50 -0700 you wrote:
> The commit under the Fixes tag added a netdev_assert_locked() in
> bnxt_free_ntp_fltrs(). The lock should be held during normal run-time
> but the assert will be triggered (see below) during bnxt_remove_one()
> which should not need the lock. The netdev is already unregistered by
> then. Fix it by calling netdev_assert_locked_or_invisible() which will
> not assert if the netdev is unregistered.
>
> [...]
Here is the summary with links:
- [net,v2] bnxt_en: Fix lockdep warning during rmmod
https://git.kernel.org/netdev/net/c/4611d88a37cf
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:[~2025-08-19 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 18:38 [PATCH net v2] bnxt_en: Fix lockdep warning during rmmod Michael Chan
2025-08-17 13:21 ` Vadim Fedorenko
2025-08-19 1:00 ` 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=175556520776.2966773.2798007329883348467.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sdf@fomichev.me \
/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