[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164792761056.20534.2752037495326713572.git-patchwork-notify@kernel.org>
Date: Tue, 22 Mar 2022 05:40:10 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Aaron Conole <aconole@...hat.com>
Cc: netdev@...r.kernel.org, dev@...nvswitch.org, pshelar@....org,
i.maximets@....org, dceara@...hat.com, nusiddiq@...hat.com,
echaudro@...hat.com
Subject: Re: [PATCH net v2] openvswitch: always update flow key after nat
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 18 Mar 2022 08:43:19 -0400 you wrote:
> During NAT, a tuple collision may occur. When this happens, openvswitch
> will make a second pass through NAT which will perform additional packet
> modification. This will update the skb data, but not the flow key that
> OVS uses. This means that future flow lookups, and packet matches will
> have incorrect data. This has been supported since
> 5d50aa83e2c8 ("openvswitch: support asymmetric conntrack").
>
> [...]
Here is the summary with links:
- [net,v2] openvswitch: always update flow key after nat
https://git.kernel.org/netdev/net/c/60b44ca6bd75
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