From: patchwork-bot+netdevbpf@kernel•org
To: Ilya Maximets <i.maximets@ovn•org>
Cc: netdev@vger•kernel.org, kuba@kernel•org, davem@davemloft•net,
dev@openvswitch•org, linux-kernel@vger•kernel.org,
pabeni@redhat•com, pshelar@ovn•org, azhou@ovn•org,
pkusunyifeng@gmail•com
Subject: Re: [PATCH net] net: openvswitch: don't send internal clone attribute to the userspace.
Date: Wed, 06 Apr 2022 01:20:11 +0000 [thread overview]
Message-ID: <164920801199.3942.3063131772130924818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220404104150.2865736-1-i.maximets@ovn.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 4 Apr 2022 12:41:50 +0200 you wrote:
> 'OVS_CLONE_ATTR_EXEC' is an internal attribute that is used for
> performance optimization inside the kernel. It's added by the kernel
> while parsing user-provided actions and should not be sent during the
> flow dump as it's not part of the uAPI.
>
> The issue doesn't cause any significant problems to the ovs-vswitchd
> process, because reported actions are not really used in the
> application lifecycle and only supposed to be shown to a human via
> ovs-dpctl flow dump. However, the action list is still incorrect
> and causes the following error if the user wants to look at the
> datapath flows:
>
> [...]
Here is the summary with links:
- [net] net: openvswitch: don't send internal clone attribute to the userspace.
https://git.kernel.org/netdev/net/c/3f2a3050b4a3
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-04-06 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:41 [PATCH net] net: openvswitch: don't send internal clone attribute to the userspace Ilya Maximets
2022-04-05 12:58 ` [ovs-dev] " Aaron Conole
2022-04-06 1: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=164920801199.3942.3063131772130924818.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=azhou@ovn$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dev@openvswitch$(echo .)org \
--cc=i.maximets@ovn$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pkusunyifeng@gmail$(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