From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot+bfab43087ad57222ce96@syzkaller.appspotmail.com,
razor@blackwall.org, idosch@nvidia.com
Subject: Re: [PATCH v3 net] net: bridge: annotate data-races around fdb->{updated,used}
Date: Sat, 10 Jan 2026 01:40:06 +0000 [thread overview]
Message-ID: <176800920629.446502.13134188823510819845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260108093806.834459-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Jan 2026 09:38:06 +0000 you wrote:
> fdb->updated and fdb->used are read and written locklessly.
>
> Add READ_ONCE()/WRITE_ONCE() annotations.
>
> Fixes: 31cbc39b6344 ("net: bridge: add option to allow activity notifications for any fdb entries")
> Reported-by: syzbot+bfab43087ad57222ce96@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/netdev/695e3d74.050a0220.1c677c.035f.GAE@google.com/
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
> Cc: Ido Schimmel <idosch@nvidia.com>
>
> [...]
Here is the summary with links:
- [v3,net] net: bridge: annotate data-races around fdb->{updated,used}
https://git.kernel.org/netdev/net/c/b25a0b4a2193
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-01-10 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 9:38 [PATCH v3 net] net: bridge: annotate data-races around fdb->{updated,used} Eric Dumazet
2026-01-08 11:41 ` Ido Schimmel
2026-01-10 1: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=176800920629.446502.13134188823510819845.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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 \
--cc=syzbot+bfab43087ad57222ce96@syzkaller.appspotmail.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