From: patchwork-bot+netdevbpf@kernel•org
To: Nikolay Aleksandrov <razor@blackwall•org>
Cc: netdev@vger•kernel.org, tobias@waldekranz•com, idosch@nvidia•com,
kuba@kernel•org, davem@davemloft•net, bridge@lists•linux.dev,
pabeni@redhat•com, edumazet@google•com, horms@kernel•org,
petrm@nvidia•com
Subject: Re: [PATCH net v2 0/2] net: bridge: fix two MST bugs
Date: Thu, 06 Nov 2025 15:40:17 +0000 [thread overview]
Message-ID: <176244361750.255671.13047904965376024193.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105111919.1499702-1-razor@blackwall.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 5 Nov 2025 13:19:17 +0200 you wrote:
> Hi,
> Patch 01 fixes a race condition that exists between expired fdb deletion
> and port deletion when MST is enabled. Learning can happen after the
> port's state has been changed to disabled which could lead to that
> port's memory being used after it's been freed. The issue was reported
> by syzbot, more information in patch 01. Patch 02 fixes an issue with
> MST's static key which Ido spotted, we can have multiple bridges with MST
> and a single bridge can erroneously disable it for all.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: bridge: fix use-after-free due to MST port state bypass
https://git.kernel.org/netdev/net/c/8dca36978aa8
- [net,v2,2/2] net: bridge: fix MST static key usage
https://git.kernel.org/netdev/net/c/ee87c63f9b2a
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:[~2025-11-06 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 11:19 [PATCH net v2 0/2] net: bridge: fix two MST bugs Nikolay Aleksandrov
2025-11-05 11:19 ` [PATCH net v2 1/2] net: bridge: fix use-after-free due to MST port state bypass Nikolay Aleksandrov
2025-11-05 16:59 ` Ido Schimmel
2025-11-05 11:19 ` [PATCH net v2 2/2] net: bridge: fix MST static key usage Nikolay Aleksandrov
2025-11-05 17:04 ` Ido Schimmel
2025-11-06 15: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=176244361750.255671.13047904965376024193.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bridge@lists$(echo .)linux.dev \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=tobias@waldekranz$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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