From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <weir@nebusec.ai>
Cc: bridge@lists.linux.dev, netdev@vger.kernel.org,
razor@blackwall.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, vega@nebusec.ai, petalzu987@gmail.com
Subject: Re: [PATCH net 0/1] net: bridge: avoid recursive multicast cleanup
Date: Mon, 05 Oct 2026 02:40:05 +0000 [thread overview]
Message-ID: <179116800528.1069246.11562984465867520213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1790323012.git.petalzu987@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sun, 27 Sep 2026 01:04:38 +0800 you wrote:
> From: Zixuan Chai <petalzu987@gmail.com>
>
> Hi Linux kernel maintainers,
>
> We found and validated an issue in net/bridge/br_multicast.c. The bug is
> reachable by a non-root user via user and network namespaces. We've tested
> it, and it should not affect any other bridge multicast functionality.
>
> [...]
Here is the summary with links:
- [net,1/1] net: bridge: avoid recursive multicast port cleanup
https://git.kernel.org/netdev/net/c/5158353121ba
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-10-05 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 17:04 [PATCH net 0/1] net: bridge: avoid recursive multicast cleanup Ren Wei
2026-09-26 17:04 ` [PATCH net 1/1] net: bridge: avoid recursive multicast port cleanup Ren Wei
2026-09-27 16:30 ` [PATCH net 0/1] net: bridge: avoid recursive multicast cleanup Andrew Lunn
2026-09-27 19:35 ` Zixuan Chai
2026-09-29 7:44 ` Nikolay Aleksandrov
2026-10-05 2: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=179116800528.1069246.11562984465867520213.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petalzu987@gmail.com \
--cc=razor@blackwall.org \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
/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