Ethernet Bridge development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhiling Zou <zhilinz@nebusec.ai>
Cc: razor@blackwall.org, bridge@lists.linux.dev,
	netdev@vger.kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	henrik.bjoernlund@microchip.com, horatiu.vultur@microchip.com,
	vega@nebusec.ai, zylzyl2333@gmail.com
Subject: Re: [PATCH net v3 0/1] net: bridge: use option bits for CFM/MRP frame handlers
Date: Wed, 09 Sep 2026 01:00:15 +0000	[thread overview]
Message-ID: <178891561534.92311.10499122115839665725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1788417901.git.zhilinz@nebusec.ai>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  3 Sep 2026 14:56:13 +0800 you wrote:
> Hi Linux kernel maintainers,
> 
> We found and validated an issue in net/bridge/br_cfm.c and
> net/bridge/br_mrp.c. The bug is reachable by a non-root user via user
> and net namespace.
> 
> We've tested it, and it should not affect any other functionality.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] net: bridge: use option bits for CFM/MRP frame handlers
    https://git.kernel.org/netdev/net/c/7a49e6b16f36

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-09  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  6:56 [PATCH net v3 0/1] net: bridge: use option bits for CFM/MRP frame handlers Zhiling Zou
2026-09-03  6:56 ` [PATCH net v3 1/1] " Zhiling Zou
2026-09-03  7:28   ` Nikolay Aleksandrov
2026-09-09  1:00 ` 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=178891561534.92311.10499122115839665725.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=henrik.bjoernlund@microchip.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@nebusec.ai \
    --cc=zylzyl2333@gmail.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