From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, pshelar@ovn.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
joe@ovn.org, jarno@ovn.org, dev@openvswitch.org,
linux-kernel@vger.kernel.org, antonin.bas@broadcom.com
Subject: Re: [PATCH net] net: openvswitch: fix overwriting ct original tuple for ICMPv6
Date: Sat, 11 May 2024 02:30:33 +0000 [thread overview]
Message-ID: <171539463384.29955.8815078625887290807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240509094228.1035477-1-i.maximets@ovn.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 May 2024 11:38:05 +0200 you wrote:
> OVS_PACKET_CMD_EXECUTE has 3 main attributes:
> - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format.
> - OVS_PACKET_ATTR_PACKET - Binary packet content.
> - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.
>
> OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure
> with the metadata like conntrack state, input port, recirculation id,
> etc. Then the packet itself gets parsed to populate the rest of the
> keys from the packet headers.
>
> [...]
Here is the summary with links:
- [net] net: openvswitch: fix overwriting ct original tuple for ICMPv6
https://git.kernel.org/netdev/net/c/7c988176b6c1
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-05-11 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:38 [PATCH net] net: openvswitch: fix overwriting ct original tuple for ICMPv6 Ilya Maximets
2024-05-09 17:18 ` Antonin Bas
2024-05-09 19:07 ` [ovs-dev] " Aaron Conole
2024-05-10 6:25 ` Eelco Chaudron
2024-05-11 2:30 ` 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=171539463384.29955.8815078625887290807.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=antonin.bas@broadcom.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=jarno@ovn.org \
--cc=joe@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 \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).