From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux.dev,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, razor@blackwall.org, horms@kernel.org,
sdf@fomichev.me
Subject: Re: [PATCH net 0/3] bridge: Fix sleep in atomic context
Date: Thu, 28 May 2026 00:30:10 +0000 [thread overview]
Message-ID: <177992821039.694601.7451967203555108525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260526064818.272516-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 May 2026 09:48:15 +0300 you wrote:
> Under certain circumstances the bridge driver can call
> dev_set_promiscuity() while holding the bridge spin lock. This is a
> problem as dev_set_promiscuity() might sleep.
>
> Patches #1-#2 fix the problem in the netlink and sysfs configuration
> paths by only taking the lock where it is actually needed, thereby
> avoiding calling dev_set_promiscuity() from an atomic context.
>
> [...]
Here is the summary with links:
- [net,1/3] bridge: Fix sleep in atomic context in netlink path
https://git.kernel.org/netdev/net/c/5eec4427b89c
- [net,2/3] bridge: Fix sleep in atomic context in sysfs path
https://git.kernel.org/netdev/net/c/6d34594cc619
- [net,3/3] selftests: rtnetlink: Add bridge promiscuity tests
https://git.kernel.org/netdev/net/c/147f3b1f23cb
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:[~2026-05-28 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 6:48 [PATCH net 0/3] bridge: Fix sleep in atomic context Ido Schimmel
2026-05-26 6:48 ` [PATCH net 1/3] bridge: Fix sleep in atomic context in netlink path Ido Schimmel
2026-05-26 6:48 ` [PATCH net 2/3] bridge: Fix sleep in atomic context in sysfs path Ido Schimmel
2026-05-26 6:48 ` [PATCH net 3/3] selftests: rtnetlink: Add bridge promiscuity tests Ido Schimmel
2026-05-27 8:25 ` Ido Schimmel
2026-05-28 0:30 ` 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=177992821039.694601.7451967203555108525.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--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