From: patchwork-bot+netdevbpf@kernel•org
To: Xin Long <lucien.xin@gmail•com>
Cc: netdev@vger•kernel.org, dev@openvswitch•org, davem@davemloft•net,
kuba@kernel•org, edumazet@google•com, pabeni@redhat•com,
pshelar@ovn•org, i.maximets@ovn•org, aconole@redhat•com,
fw@strlen•de, marcelo.leitner@gmail•com
Subject: Re: [PATCH net] openvswitch: get related ct labels from its master if it is not confirmed
Date: Fri, 21 Jun 2024 09:20:29 +0000 [thread overview]
Message-ID: <171896162949.20195.7630487856470718587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <48a6cd8c4f9c6bf6f0314d992d61c65b43cb3983.1718834936.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft•net>:
On Wed, 19 Jun 2024 18:08:56 -0400 you wrote:
> Ilya found a failure in running check-kernel tests with at_groups=144
> (144: conntrack - FTP SNAT orig tuple) in OVS repo. After his further
> investigation, the root cause is that the labels sent to userspace
> for related ct are incorrect.
>
> The labels for unconfirmed related ct should use its master's labels.
> However, the changes made in commit 8c8b73320805 ("openvswitch: set
> IPS_CONFIRMED in tmpl status only when commit is set in conntrack")
> led to getting labels from this related ct.
>
> [...]
Here is the summary with links:
- [net] openvswitch: get related ct labels from its master if it is not confirmed
https://git.kernel.org/netdev/net/c/a23ac973f67f
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:[~2024-06-21 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 22:08 [PATCH net] openvswitch: get related ct labels from its master if it is not confirmed Xin Long
2024-06-20 17:14 ` Ilya Maximets
2024-06-20 19:00 ` [ovs-dev] " Aaron Conole
2024-06-21 9:20 ` 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=171896162949.20195.7630487856470718587.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=aconole@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dev@openvswitch$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=i.maximets@ovn$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lucien.xin@gmail$(echo .)com \
--cc=marcelo.leitner@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pshelar@ovn$(echo .)org \
/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