From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, pshelar@ovn.org, davem@davemloft.net,
dev@openvswitch.org, linux-kernel@vger.kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
aconole@redhat.com, pvalerio@redhat.com, stable@vger.kernel.org,
frode.nordahl@canonical.com
Subject: Re: [PATCH net] net: openvswitch: fix misuse of the cached connection on tuple changes
Date: Thu, 09 Jun 2022 04:00:13 +0000 [thread overview]
Message-ID: <165474721335.28317.13891596289407193107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220606221140.488984-1-i.maximets@ovn.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Jun 2022 00:11:40 +0200 you wrote:
> If packet headers changed, the cached nfct is no longer relevant
> for the packet and attempt to re-use it leads to the incorrect packet
> classification.
>
> This issue is causing broken connectivity in OpenStack deployments
> with OVS/OVN due to hairpin traffic being unexpectedly dropped.
>
> [...]
Here is the summary with links:
- [net] net: openvswitch: fix misuse of the cached connection on tuple changes
https://git.kernel.org/netdev/net/c/2061ecfdf235
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-06-09 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 22:11 [PATCH net] net: openvswitch: fix misuse of the cached connection on tuple changes Ilya Maximets
2022-06-09 4: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=165474721335.28317.13891596289407193107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=frode.nordahl@canonical.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=pvalerio@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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