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,
dsahern@kernel.org, yongwang@nvidia.com, aroulin@nvidia.com,
petrm@nvidia.com, tglx@kernel.org
Subject: Re: [PATCH net 0/2] bridge: mcast: Fix a possible use-after-free when removing a bridge port
Date: Wed, 20 May 2026 01:30:09 +0000 [thread overview]
Message-ID: <177924060914.2943546.7719678973905052337.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260517121122.188333-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 17 May 2026 15:11:20 +0300 you wrote:
> Patch #1 fixes a possible use-after-free when removing a bridge port.
>
> Patch #2 adds a test case that triggers the problem.
>
> In net-next we can:
>
> 1. Add DEBUG_NET_WARN_ON_ONCE() when a port multicast context is
> de-initialized while enabled.
>
> [...]
Here is the summary with links:
- [net,1/2] bridge: mcast: Fix a possible use-after-free when removing a bridge port
https://git.kernel.org/netdev/net/c/4df78ff02629
- [net,2/2] selftests: bridge_vlan_mcast: Test toggling of multicast snooping
https://git.kernel.org/netdev/net/c/ae743a8ca8db
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-20 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 12:11 [PATCH net 0/2] bridge: mcast: Fix a possible use-after-free when removing a bridge port Ido Schimmel
2026-05-17 12:11 ` [PATCH net 1/2] " Ido Schimmel
2026-05-19 9:31 ` Ido Schimmel
2026-05-17 12:11 ` [PATCH net 2/2] selftests: bridge_vlan_mcast: Test toggling of multicast snooping Ido Schimmel
2026-05-20 1: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=177924060914.2943546.7719678973905052337.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aroulin@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=tglx@kernel.org \
--cc=yongwang@nvidia.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