From: Minxi Hou <houminxi@gmail.com>
To: kuba@kernel.org
Cc: netdev@vger.kernel.org, donald.hunter@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org
Subject: Re: [PATCH net-next v3 1/2] netlink: specs: add ovs_flow del and set operations
Date: Wed, 21 Oct 2026 01:45:29 -0400 [thread overview]
Message-ID: <20261021054529.1857897-1-houminxi@gmail.com> (raw)
In-Reply-To: <20261020202440.1012706-1-kuba@kernel.org>
On Tue, 20 Oct 2026 16:24:40 -0400 Jakub Kicinski wrote:
> Should include/uapi/linux/openvswitch.h get the same update?
Yes, the kernel-doc for OVS_FLOW_ATTR_KEY still says a key is required
for every request except a dump, and the kernel does not enforce that.
The header is a kernel change, so I will send it separately rather than
fold it into this series.
> Could the doc mention those two cases as well?
Yes. A dump reads neither a key nor a ufid, and a del that carries
neither flushes the data path. The next version says both.
> is "Always present in notifications" accurate?
It is not. A ufid-identified flow with OVS_UFID_F_OMIT_KEY set has no
key in the reply. The sentence was already in the spec and in the
header, and this patch only kept it. I will correct it with the header
change.
> Should this change carry a tag like:
> Fixes: 93b230b549bc ("netlink: specs: add ynl spec for ovs_flow")
> Could it also go in a separate patch
I would rather keep it here. del and set both list probe, so splitting
the type fix out would leave them pointing at an attribute the spec
still encodes wrong. I have not added a Fixes tag for the same reason:
the change belongs with the operations that use the attribute.
next prev parent reply other threads:[~2026-10-21 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 2:41 [PATCH net-next v3 0/2] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-10-15 2:41 ` [PATCH net-next v3 1/2] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-10-20 20:24 ` Jakub Kicinski
2026-10-21 5:45 ` Minxi Hou [this message]
2026-10-15 2:41 ` [PATCH net-next v3 2/2] netlink: specs: add ovs datapath and vport " Minxi Hou
2026-10-20 20:24 ` Jakub Kicinski
2026-10-21 5:45 ` 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=20261021054529.1857897-1-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--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