From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
Ilya Maximets <i.maximets@ovn.org>
Subject: [PATCH net-next v8 1/3] netlink: specs: add ovs_flow del and set operations
Date: Sun, 15 Nov 2026 02:26:36 -0500 [thread overview]
Message-ID: <20261115072638.3163018-2-houminxi@gmail.com> (raw)
In-Reply-To: <20261115072638.3163018-1-houminxi@gmail.com>
The ovs_flow spec described get and new only, so a YNL client could not
delete or modify a flow. Both commands have been in the kernel since the
family was added: del flushes the data path when a request carries neither
a key nor a ufid, or no key and a ufid longer than 16 octets, and set looks
a flow up by key or by ufid.
List the attributes each command reads, and say that a successful delete of
one flow, or a successful set, sends that flow to the family's multicast
group, as the kernel does. new and get read ufid-flags and probe as well as
the key, so those belong in their request lists. The get reply gains the
last-used time and the TCP flags, which ovs_flow_cmd_fill_stats() fills for
a get and for a dump reply. new, del and set need CAP_NET_ADMIN, and all
four operations skip strict and dump validation.
A dump reads ufid-flags alone, so give it a request list of its own instead
of sharing the get list. The reply stays the same as for get.
probe was binary while the kernel policy is NLA_FLAG, so a client that
wanted to raise it had to send an attribute with no body. As a flag the
generated setter takes no value.
The key, actions, stats, used and tcp-flags docs called those attributes
always present in notifications. The key is left out for a flow identified
by a ufid when the request asked for the key to be left out, and a dump
also leaves the actions out when they do not fit in the message. The other
three appear in replies as well, which the docs now say, and the uapi
comments for those attributes say the same.
The key doc said a key is required for every request except a dump. The
kernel accepts a ufid with no key, but a get and a set need one of the two,
and a set that replaces the actions needs a key. A new request needs a key,
including one that finds an existing flow and replaces its actions.
The header definition said a zero data path member leaves the request
non-specific, which no flow request accepts: each of them returns -ENODEV.
Drop that description.
The ufid doc promised that the flow is indexed by that value, which does
not hold for a value the kernel rejects. A value longer than 16 octets is
read as if the attribute were absent, so a new request indexes the flow by
its key instead, and a del that carries no key flushes the data path. A
zero length value fails the minimum length the policy sets. Record that
minimum, and limit the promise about indexing to a value the kernel
accepts. The doc also said the attribute appears in notifications only,
while a reply carries it too.
Signed-off-by: Minxi Hou <houminxi@gmail.com>
---
Documentation/netlink/specs/ovs_flow.yaml | 110 +++++++++++++++++-----
include/uapi/linux/openvswitch.h | 35 ++++---
2 files changed, 109 insertions(+), 36 deletions(-)
diff --git a/Documentation/netlink/specs/ovs_flow.yaml b/Documentation/netlink/specs/ovs_flow.yaml
index 951837b72e1d..98ef461535cd 100644
--- a/Documentation/netlink/specs/ovs_flow.yaml
+++ b/Documentation/netlink/specs/ovs_flow.yaml
@@ -18,9 +18,6 @@ definitions:
-
name: dp-ifindex
type: u32
- doc: |
- ifindex of local port for datapath (0 to make a request not specific
- to a datapath).
-
name: ovs-flow-stats
type: struct
@@ -383,41 +380,50 @@ attribute-sets:
type: nest
nested-attributes: key-attrs
doc: |
- Nested attributes specifying the flow key. Always present in
- notifications. Required for all requests (except dumps).
+ Nested attributes specifying the flow key. Present in replies and
+ notifications, except for a flow identified by a ufid when the
+ request asked for the key to be left out. A get, set or del may
+ carry a ufid instead of a key; a get and a set need one of the
+ two, and a set that replaces the actions needs a key. A new
+ request needs a key, including one that finds an existing flow and
+ replaces its actions. A del that carries neither a key nor a ufid
+ flushes the data path, and so does one that carries no key and a
+ ufid longer than 16 octets.
-
name: actions
type: nest
nested-attributes: action-attrs
doc: |
Nested attributes specifying the actions to take for packets that
- match the key. Always present in notifications. Required for
- OVS_FLOW_CMD_NEW requests, optional for OVS_FLOW_CMD_SET requests. An
- OVS_FLOW_CMD_SET without OVS_FLOW_ATTR_ACTIONS will not modify the
- actions. To clear the actions, an OVS_FLOW_ATTR_ACTIONS without any
- nested attributes must be given.
+ match the key. Present in replies and notifications, except when
+ the request asked for the actions to be left out, and in a dump
+ when they do not fit in the message. Required for
+ OVS_FLOW_CMD_NEW requests, optional for OVS_FLOW_CMD_SET requests.
+ An OVS_FLOW_CMD_SET without OVS_FLOW_ATTR_ACTIONS will not modify
+ the actions. To clear the actions, an OVS_FLOW_ATTR_ACTIONS
+ without any nested attributes must be given.
-
name: stats
type: binary
struct: ovs-flow-stats
doc: |
- Statistics for this flow. Present in notifications if the stats would
- be nonzero. Ignored in requests.
+ Statistics for this flow. Present in replies and notifications if
+ the stats would be nonzero. Ignored in requests.
-
name: tcp-flags
type: u8
doc: |
An 8-bit value giving the ORed value of all of the TCP flags seen on
- packets in this flow. Only present in notifications for TCP flows, and
- only if it would be nonzero. Ignored in requests.
+ packets in this flow. Only present in replies and notifications for
+ TCP flows, and only if it would be nonzero. Ignored in requests.
-
name: used
type: u64
doc: |
A 64-bit integer giving the time, in milliseconds on the system
monotonic clock, at which a packet was last processed for this
- flow. Only present in notifications if a packet has been processed for
- this flow. Ignored in requests.
+ flow. Only present in replies and notifications if a packet has been
+ processed for this flow. Ignored in requests.
-
name: clear
type: flag
@@ -438,18 +444,21 @@ attribute-sets:
are exact match bits.
-
name: probe
- type: binary
+ type: flag
doc: |
Flow operation is a feature probe, error logging should be suppressed.
-
name: ufid
type: binary
+ checks:
+ min-len: 1
doc: |
A value between 1-16 octets specifying a unique identifier for the
flow. Causes the flow to be indexed by this value rather than the
- value of the OVS_FLOW_ATTR_KEY attribute. Optional for all
- requests. Present in notifications if the flow was created with this
- attribute.
+ value of the OVS_FLOW_ATTR_KEY attribute. A value longer than 16
+ octets is treated as if the attribute were absent, so a new flow is
+ indexed by its key. Optional for all requests. Present in replies
+ and notifications if the flow was created with this attribute.
display-hint: uuid
-
name: ufid-flags
@@ -969,25 +978,77 @@ operations:
doc: Get / dump OVS flow configuration and state
value: 3
attribute-set: flow-attrs
- do: &flow-get-op
+ dont-validate: [strict, dump]
+ do:
request:
attributes:
- key
- ufid
- ufid-flags
- reply:
+ - probe
+ reply: &flow-get-reply
attributes:
- key
- ufid
- mask
+ - used
- stats
+ - tcp-flags
- actions
- dump: *flow-get-op
+ dump:
+ request:
+ attributes:
+ - ufid-flags
+ reply: *flow-get-reply
-
name: new
doc: Create OVS flow configuration in a data path
value: 1
attribute-set: flow-attrs
+ dont-validate: [strict, dump]
+ flags: [uns-admin-perm]
+ do:
+ request:
+ attributes:
+ - key
+ - ufid
+ - mask
+ - actions
+ - ufid-flags
+ - probe
+ -
+ name: del
+ doc: |
+ Delete one flow, or every flow in the data path. A request that
+ carries neither a key nor a ufid flushes the data path, and so does
+ one that carries no key and a ufid longer than 16 octets. A
+ successful delete of a single flow also sends that flow to the
+ family's multicast group, and to the requester when the request
+ sets NLM_F_ECHO; a flush sends nothing.
+ value: 2
+ attribute-set: flow-attrs
+ dont-validate: [strict, dump]
+ flags: [uns-admin-perm]
+ do:
+ request:
+ attributes:
+ - key
+ - ufid
+ - ufid-flags
+ - probe
+ -
+ name: set
+ doc: |
+ Modify an existing flow. The kernel rejects the request with
+ -EINVAL when it carries neither a key nor a ufid. Replacing the
+ actions also needs a key: a ufid on its own is not enough. A
+ successful set also sends the updated flow to the family's
+ multicast group, and to the requester when the request sets
+ NLM_F_ECHO.
+ value: 4
+ attribute-set: flow-attrs
+ dont-validate: [strict, dump]
+ flags: [uns-admin-perm]
do:
request:
attributes:
@@ -995,6 +1056,9 @@ operations:
- ufid
- mask
- actions
+ - ufid-flags
+ - clear
+ - probe
mcast-groups:
list:
diff --git a/include/uapi/linux/openvswitch.h b/include/uapi/linux/openvswitch.h
index 440825e65837..bd77e6fb4a95 100644
--- a/include/uapi/linux/openvswitch.h
+++ b/include/uapi/linux/openvswitch.h
@@ -624,24 +624,32 @@ struct ovs_nsh_key_md1 {
/**
* enum ovs_flow_attr - attributes for %OVS_FLOW_* commands.
* @OVS_FLOW_ATTR_KEY: Nested %OVS_KEY_ATTR_* attributes specifying the flow
- * key. Always present in notifications. Required for all requests (except
- * dumps).
+ * key. Present in replies and notifications, except for a flow identified
+ * by a ufid when the request asked for the key to be left out. A get, set
+ * or del may carry a ufid instead of a key; a get and a set need one of the
+ * two, and a set that replaces the actions needs a key. A new request needs
+ * a key, including one that finds an existing flow and replaces its
+ * actions. A del carrying neither a key nor a ufid flushes the data path,
+ * as does one carrying no key and a ufid longer than 16 octets.
* @OVS_FLOW_ATTR_ACTIONS: Nested %OVS_ACTION_ATTR_* attributes specifying
- * the actions to take for packets that match the key. Always present in
- * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
+ * the actions to take for packets that match the key. Present in replies
+ * and notifications, except when the request asked for the actions to be
+ * left out, and in a dump when they do not fit in the message. Required
+ * for %OVS_FLOW_CMD_NEW requests, optional for
* %OVS_FLOW_CMD_SET requests. An %OVS_FLOW_CMD_SET without
* %OVS_FLOW_ATTR_ACTIONS will not modify the actions. To clear the actions,
* an %OVS_FLOW_ATTR_ACTIONS without any nested attributes must be given.
* @OVS_FLOW_ATTR_STATS: &struct ovs_flow_stats giving statistics for this
- * flow. Present in notifications if the stats would be nonzero. Ignored in
- * requests.
+ * flow. Present in replies and notifications if the stats would be nonzero.
+ * Ignored in requests.
* @OVS_FLOW_ATTR_TCP_FLAGS: An 8-bit value giving the OR'd value of all of the
- * TCP flags seen on packets in this flow. Only present in notifications for
- * TCP flows, and only if it would be nonzero. Ignored in requests.
+ * TCP flags seen on packets in this flow. Only present in replies and
+ * notifications for TCP flows, and only if it would be nonzero. Ignored in
+ * requests.
* @OVS_FLOW_ATTR_USED: A 64-bit integer giving the time, in milliseconds on
* the system monotonic clock, at which a packet was last processed for this
- * flow. Only present in notifications if a packet has been processed for this
- * flow. Ignored in requests.
+ * flow. Only present in replies and notifications if a packet has been
+ * processed for this flow. Ignored in requests.
* @OVS_FLOW_ATTR_CLEAR: If present in a %OVS_FLOW_CMD_SET request, clears the
* last-used time, accumulated TCP flags, and statistics for this flow.
* Otherwise ignored in requests. Never present in notifications.
@@ -655,9 +663,10 @@ struct ovs_nsh_key_md1 {
* should be suppressed.
* @OVS_FLOW_ATTR_UFID: A value between 1-16 octets specifying a unique
* identifier for the flow. Causes the flow to be indexed by this value rather
- * than the value of the %OVS_FLOW_ATTR_KEY attribute. Optional for all
- * requests. Present in notifications if the flow was created with this
- * attribute.
+ * than the value of the %OVS_FLOW_ATTR_KEY attribute. A value longer than 16
+ * octets is treated as if the attribute were absent, so a new flow is indexed
+ * by its key. Optional for all requests. Present in replies and notifications
+ * if the flow was created with this attribute.
* @OVS_FLOW_ATTR_UFID_FLAGS: A 32-bit value of OR'd %OVS_UFID_F_*
* flags that provide alternative semantics for flow installation and
* retrieval. Optional for all requests.
--
2.56.0
next prev parent reply other threads:[~2026-11-15 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 7:26 [PATCH net-next v8 0/3] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-11-15 7:26 ` Minxi Hou [this message]
2026-11-15 7:26 ` [PATCH net-next v8 2/3] netlink: specs: add ovs datapath and vport set operations Minxi Hou
2026-11-15 7:26 ` [PATCH net-next v8 3/3] netlink: specs: correct the ovs specs where they do not match the kernel 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=20261115072638.3163018-2-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=echaudro@redhat.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.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