Re: [PATCH net-next v9 0/3] netlink: specs: fill in the missing ovs operations
From: patchwork-bot+netdevbpf
Date: Sat Nov 21 2026 - 18:50:12 EST
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:
On Thu, 19 Nov 2026 12:21:15 -0500 you wrote:
> The ovs specs describe get and new but not every command the kernel
> has registered: all three families lacked set, and ovs_flow also lacked
> del. This series adds them, names the attributes each handler reads,
> and corrects what the existing specs say about the kernel. No kernel
> code changes.
>
> v9:
> https://lore.kernel.org/netdev/20261115072638.3163018-1-houminxi@xxxxxxxxx/
> - Rebased onto current net-next.
> - The note on the vport name is a complete sentence again. The v8
> wording stopped after "dp_ifindex from", so the sentence that says
> what the lookup falls back to was missing.
> v8:
> https://lore.kernel.org/netdev/20261110174751.973464-1@xxxxxxxxx/
> - The datapath spec no longer puts a maximum on masks-cache-size. The
> generator does not turn a check into a policy for these families, and
> the kernel bound is an expression, so the declaration promised
> something the spec cannot express.
> - The docs no longer say what a dump does with a key, a ufid or another
> request attribute. A dump now has its own request list for each family,
> which states what it takes, so the sentences that repeated it are gone.
> The ufid docs record the minimum length the policy sets, and the key,
> actions, stats, used and tcp-flags docs say the attributes appear in
> replies as well as in notifications.
> - The series gains a third patch for gaps that predate it. The vport
> netnsid is signed in the kernel. The two dumps stop sharing a request
> list with their get operation, and four lists named attributes their
> handler never reads or sends. The vport get request can be answered by
> port number, and the vport new doc says an ifindex needs an internal
> vport. The vport spec declared family version 2 where the kernel
> registers 1.
> - That patch also declares what the kernel registers: all four ovs specs
> document the header struct and none of them a member of it, the vport
> name note names the header member the lookup uses, the options note
> says what a set returns, the packet execute operation gains the
> validate flags and the admin permission, and the ynl selftest stops
> printing a field the datapath reply does not carry.
> - Deleting one flow sends that flow to the family's multicast group, a
> flush sends nothing, and the set operations do the same for the object
> they change, which those op docs now say.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/3] netlink: specs: add ovs_flow del and set operations
https://git.kernel.org/netdev/net-next/c/a07bb1cee2af
- [net-next,v9,2/3] netlink: specs: add ovs datapath and vport set operations
https://git.kernel.org/netdev/net-next/c/fa2ea983e25d
- [net-next,v9,3/3] netlink: specs: correct the ovs specs where they do not match the kernel
https://git.kernel.org/netdev/net-next/c/f53c4f7ecfcc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html