From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com, idosch@nvidia.com,
syzkaller@googlegroups.com
Subject: Re: [PATCH net 1/2] ipv4: fix data races in fib_alias_hw_flags_set
Date: Thu, 17 Feb 2022 18:10:11 +0000 [thread overview]
Message-ID: <164512141153.19163.18168888895219925303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220216173217.3792411-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Feb 2022 09:32:16 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> fib_alias_hw_flags_set() can be used by concurrent threads,
> and is only RCU protected.
>
> We need to annotate accesses to following fields of struct fib_alias:
>
> [...]
Here is the summary with links:
- [net,1/2] ipv4: fix data races in fib_alias_hw_flags_set
https://git.kernel.org/netdev/net/c/9fcf986cc4bc
- [net,2/2] ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt
https://git.kernel.org/netdev/net/c/d95d6320ba7a
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:[~2022-02-17 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:32 [PATCH net 1/2] ipv4: fix data races in fib_alias_hw_flags_set Eric Dumazet
2022-02-16 17:32 ` [PATCH net 2/2] ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt Eric Dumazet
2022-02-16 21:30 ` [PATCH net 1/2] ipv4: fix data races in fib_alias_hw_flags_set Ido Schimmel
2022-02-17 18:10 ` 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=164512141153.19163.18168888895219925303.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=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.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