From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
dan.carpenter@linaro.org
Subject: Re: [PATCH net v3 0/7] eth: fix calling napi_enable() in atomic context
Date: Mon, 27 Jan 2025 22:40:33 +0000 [thread overview]
Message-ID: <173801763301.3245248.16328170214017560223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250124031841.1179756-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Jan 2025 19:18:34 -0800 you wrote:
> Dan has reported that I missed a lot of drivers which call napi_enable()
> in atomic with the naive coccinelle search for spin locks:
> https://lore.kernel.org/dcfd56bc-de32-4b11-9e19-d8bd1543745d@stanley.mountain
>
> Fix them. Most of the fixes involve taking the netdev_lock()
> before the spin lock. mt76 is special because we can just
> move napi_enable() from the BH section.
>
> [...]
Here is the summary with links:
- [net,v3,1/7] eth: tg3: fix calling napi_enable() in atomic context
https://git.kernel.org/netdev/net/c/8ed47e4e0b42
- [net,v3,2/7] eth: forcedeth: remove local wrappers for napi enable/disable
https://git.kernel.org/netdev/net/c/a878f3e4ace7
- [net,v3,3/7] eth: forcedeth: fix calling napi_enable() in atomic context
https://git.kernel.org/netdev/net/c/5c4470a1719c
- [net,v3,4/7] eth: 8139too: fix calling napi_enable() in atomic context
https://git.kernel.org/netdev/net/c/d19e612c47f4
- [net,v3,5/7] eth: niu: fix calling napi_enable() in atomic context
https://git.kernel.org/netdev/net/c/f1d12bc7a596
- [net,v3,6/7] eth: via-rhine: fix calling napi_enable() in atomic context
https://git.kernel.org/netdev/net/c/09a939487fc8
- [net,v3,7/7] wifi: mt76: move napi_enable() from under BH
https://git.kernel.org/netdev/net/c/a60558644e20
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-01-27 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 3:18 [PATCH net v3 0/7] eth: fix calling napi_enable() in atomic context Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 1/7] eth: tg3: " Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 2/7] eth: forcedeth: remove local wrappers for napi enable/disable Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 3/7] eth: forcedeth: fix calling napi_enable() in atomic context Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 4/7] eth: 8139too: " Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 5/7] eth: niu: " Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 6/7] eth: via-rhine: " Jakub Kicinski
2025-01-24 3:18 ` [PATCH net v3 7/7] wifi: mt76: move napi_enable() from under BH Jakub Kicinski
2025-01-27 22:40 ` 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=173801763301.3245248.16328170214017560223.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).