[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<168984122042.2934.17630490414309506101.git-patchwork-notify@kernel.org>
Date: Thu, 20 Jul 2023 08:20:20 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Xin Long <lucien.xin@...il.com>
Cc: netdev@...r.kernel.org, dev@...nvswitch.org, davem@...emloft.net,
kuba@...nel.org, edumazet@...gle.com, pabeni@...hat.com, pshelar@....org,
jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
pablo@...filter.org, fw@...len.de, marcelo.leitner@...il.com,
dcaratti@...hat.com, aconole@...hat.com
Subject: Re: [PATCH net-next 0/3] net: handle the exp removal problem with ovs
upcall properly
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Sun, 16 Jul 2023 17:09:16 -0400 you wrote:
> With the OVS upcall, the original ct in the skb will be dropped, and when
> the skb comes back from userspace it has to create a new ct again through
> nf_conntrack_in() in either OVS __ovs_ct_lookup() or TC tcf_ct_act().
>
> However, the new ct will not be able to have the exp as the original ct
> has taken it away from the hash table in nf_ct_find_expectation(). This
> will cause some flow never to be matched, like:
>
> [...]
Here is the summary with links:
- [net-next,1/3] netfilter: allow exp not to be removed in nf_ct_find_expectation
https://git.kernel.org/netdev/net-next/c/4914109a8e1e
- [net-next,2/3] net: sched: set IPS_CONFIRMED in tmpl status only when commit is set in act_ct
https://git.kernel.org/netdev/net-next/c/76622ced50a1
- [net-next,3/3] openvswitch: set IPS_CONFIRMED in tmpl status only when commit is set in conntrack
https://git.kernel.org/netdev/net-next/c/8c8b73320805
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