From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: Donald Hunter <donald.hunter@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v2 1/2] netlink: specs: add ovs_flow del and set operations
Date: Wed, 14 Oct 2026 07:03:43 -0400 [thread overview]
Message-ID: <20261014110343.2567026-1-houminxi@gmail.com> (raw)
In-Reply-To: <179187709747.434549.16040884181450649933@kernel.org>
On Tue, 13 Oct 2026, netdev-bot+sashiko@kernel.org wrote:
> [Medium] The new operation's request list still leaves out ufid-flags
> and probe. ovs_flow_cmd_new() reads both.
Yes. ovs_flow_cmd_new() reads OVS_FLOW_ATTR_UFID_FLAGS and
OVS_FLOW_ATTR_PROBE, and the del and set lists in this patch already
have them. The new list did not. v3 adds both.
> [Low] The commit message does not mention the probe type change or the
> uns-admin-perm flag added to the existing new operation.
Right, it only said del and set need CAP_NET_ADMIN. new takes the same
flag, and probe changes from binary to flag, which changes how a YNL
client encodes it. v3 says both.
> [Low] The key attribute doc says a key is required for every request
> except a dump, which contradicts the new del and set docs.
The doc was wrong. get, set and del all accept a ufid with no key, and
only a new flow needs one. A set that replaces the actions still needs
a key, which the set doc already says. v3 changes the key doc.
> [Low] The get operation uses one request list for both do and dump.
That list predates this series. get's do request reads probe and the
dump request only reads ufid-flags, so the two should not share a list.
I am leaving it for a separate patch rather than widening this one.
pw-bot: cr
next prev parent reply other threads:[~2026-10-14 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 6:55 [PATCH net-next v2 0/2] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-10-12 6:55 ` [PATCH net-next v2 1/2] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-10-13 7:38 ` netdev-bot+sashiko
2026-10-14 11:03 ` Minxi Hou [this message]
2026-10-12 6:55 ` [PATCH net-next v2 2/2] netlink: specs: add ovs datapath and vport " Minxi Hou
2026-10-13 7:38 ` netdev-bot+sashiko
-- strict thread matches above, loose matches on Subject: below --
2026-10-06 13:05 [PATCH net-next 0/2] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-10-06 13:05 ` [PATCH net-next 1/2] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-10-08 13:08 ` netdev-bot+sashiko
2026-10-09 3:25 ` Minxi Hou
2026-10-06 13:05 ` [PATCH net-next 2/2] netlink: specs: add ovs datapath and vport " Minxi Hou
2026-10-08 13:08 ` netdev-bot+sashiko
2026-10-09 3:26 ` Minxi Hou
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=20261014110343.2567026-1-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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