From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, razor@blackwall.org, horms@kernel.org
Subject: Re: [PATCH net-next] bridge: mcast: Synchronously shutdown port multicast timers
Date: Fri, 05 Jun 2026 01:20:17 +0000 [thread overview]
Message-ID: <178062241739.3090676.1203878185997865685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603103522.622411-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 3 Jun 2026 13:35:22 +0300 you wrote:
> Currently, while four timers are set up during port multicast context
> initialization, only two are synchronously deleted when the context is
> de-initialized, just before being deleted.
>
> This is fine because the structure containing the multicast context
> (either a bridge port or a VLAN) is only deleted after an RCU grace
> period and it will not pass as long as the timers are executing. These
> timers are also not supposed to do any work at this stage. They acquire
> the bridge multicast lock, see that the multicast context was disabled
> and exit.
>
> [...]
Here is the summary with links:
- [net-next] bridge: mcast: Synchronously shutdown port multicast timers
https://git.kernel.org/netdev/net-next/c/7a188fcc18d4
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-06-05 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 10:35 [PATCH net-next] bridge: mcast: Synchronously shutdown port multicast timers Ido Schimmel
2026-06-05 1:20 ` 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=178062241739.3090676.1203878185997865685.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--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 \
/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