From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org
Subject: [PATCH net-next v2 0/2] netlink: specs: fill in the missing ovs operations
Date: Mon, 12 Oct 2026 02:55:50 -0400 [thread overview]
Message-ID: <20261012065552.2426415-1-houminxi@gmail.com> (raw)
The ovs_flow spec described get and new but not del or set, and the
ovs_datapath and ovs_vport specs had no set. The kernel has registered
all three since the families were added. This series names the
operations and the attributes each handler reads, and marks the write
operations uns-admin-perm.
No kernel code changes. I checked the new operations against a live
kernel with YnlFamily before posting v1.
v2:
- ovs_flow: probe is a flag, matching the NLA_FLAG policy. It stayed
binary in v1 because no request listed it.
- ovs_flow: del lists probe. ovs_flow_cmd_del() reads it to decide
whether to log.
- ovs_flow: the set doc says that replacing actions needs a key even
when a ufid is present. ovs_nla_init_match_and_action() returns
-EINVAL otherwise.
v1: https://lore.kernel.org/netdev/20261006130533.1620706-1-houminxi@gmail.com/
Minxi Hou (2):
netlink: specs: add ovs_flow del and set operations
netlink: specs: add ovs datapath and vport set operations
Documentation/netlink/specs/ovs_datapath.yaml | 18 ++++++++++
Documentation/netlink/specs/ovs_flow.yaml | 35 ++++++++++++++++++-
Documentation/netlink/specs/ovs_vport.yaml | 15 ++++++++
3 files changed, 67 insertions(+), 1 deletion(-)
base-commit: d8674294aefef02266c4d47ad10131f1bffbe534
Signed-off-by: Minxi Hou <houminxi@gmail.com>
--
2.55.0
next reply other threads:[~2026-10-12 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 6:55 Minxi Hou [this message]
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-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
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=20261012065552.2426415-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