From: patchwork-bot+netdevbpf@kernel•org
To: Paul Blakey <paulb@nvidia•com>
Cc: dev@openvswitch•org, netdev@vger•kernel.org,
xiyou.wangcong@gmail•com, jhs@mojatatu•com, pshelar@ovn•org,
davem@davemloft•net, jiri@nvidia•com, kuba@kernel•org,
saeedm@nvidia•com, ozsh@nvidia•com, vladbu@nvidia•com,
roid@nvidia•com
Subject: Re: [PATCH net v2 1/1] net: openvswitch: Fix ct_state nat flags for conns arriving from tc
Date: Mon, 10 Jan 2022 01:00:09 +0000 [thread overview]
Message-ID: <164177640911.18208.11219008492707662501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220106153804.26451-1-paulb@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 6 Jan 2022 17:38:04 +0200 you wrote:
> Netfilter conntrack maintains NAT flags per connection indicating
> whether NAT was configured for the connection. Openvswitch maintains
> NAT flags on the per packet flow key ct_state field, indicating
> whether NAT was actually executed on the packet.
>
> When a packet misses from tc to ovs the conntrack NAT flags are set.
> However, NAT was not necessarily executed on the packet because the
> connection's state might still be in NEW state. As such, openvswitch
> wrongly assumes that NAT was executed and sets an incorrect flow key
> NAT flags.
>
> [...]
Here is the summary with links:
- [net,v2,1/1] net: openvswitch: Fix ct_state nat flags for conns arriving from tc
https://git.kernel.org/netdev/net/c/6f022c2ddbce
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-01-10 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 15:38 [PATCH net v2 1/1] net: openvswitch: Fix ct_state nat flags for conns arriving from tc Paul Blakey
2022-01-08 13:23 ` Jamal Hadi Salim
2022-01-10 1:00 ` 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=164177640911.18208.11219008492707662501.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dev@openvswitch$(echo .)org \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ozsh@nvidia$(echo .)com \
--cc=paulb@nvidia$(echo .)com \
--cc=pshelar@ovn$(echo .)org \
--cc=roid@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=vladbu@nvidia$(echo .)com \
--cc=xiyou.wangcong@gmail$(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