[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162802680646.18812.7948023061004183994.git-patchwork-notify@kernel.org>
Date: Tue, 03 Aug 2021 21:40:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
jiri@...nulli.us, idosch@...sch.org, roopa@...dia.com,
nikolay@...dia.com, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next] net: bridge: switchdev: fix incorrect use of FDB
flags when picking the dst device
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 2 Aug 2021 14:36:33 +0300 you wrote:
> Nikolay points out that it is incorrect to assume that it is impossible
> to have an fdb entry with fdb->dst == NULL and the BR_FDB_LOCAL bit in
> fdb->flags not set. This is because there are reader-side places that
> test_bit(BR_FDB_LOCAL, &fdb->flags) without the br->hash_lock, and if
> the updating of the FDB entry happens on another CPU, there are no
> memory barriers at writer or reader side which would ensure that the
> reader sees the updates to both fdb->flags and fdb->dst in the same
> order, i.e. the reader will not see an inconsistent FDB entry.
>
> [...]
Here is the summary with links:
- [net-next] net: bridge: switchdev: fix incorrect use of FDB flags when picking the dst device
https://git.kernel.org/netdev/net-next/c/2e19bb35ce15
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists