diff options
| author | Jakub Kicinski <[email protected]> | 2025-04-09 14:55:41 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2025-04-14 21:05:56 +0000 |
| commit | 747fb8413aaa36e4c988d45c4fe20d4c2b0778cd (patch) | |
| tree | b6fcb7a4cd6a387066e5933d03f52f05f56c35b0 /net/unix/af_unix.c | |
| parent | net: don't mix device locking in dev_close_many() calls (diff) | |
| download | kernel-747fb8413aaa36e4c988d45c4fe20d4c2b0778cd.tar.gz kernel-747fb8413aaa36e4c988d45c4fe20d4c2b0778cd.zip | |
netlink: specs: ovs_vport: align with C codegen capabilities
We started generating C code for OvS a while back, but actually
C codegen only supports fixed headers specified at the family
level right now (schema also allows specifying them per op).
ovs_flow and ovs_datapath already specify the fixed header
at the family level but ovs_vport does it per op.
Move the property, all ops use the same header.
This ensures YNL C sees the correct hdr_len:
const struct ynl_family ynl_ovs_vport_family = {
.name = "ovs_vport",
- .hdr_len = sizeof(struct genlmsghdr),
+ .hdr_len = sizeof(struct genlmsghdr) + sizeof(struct ovs_header),
};
Fixes: 7c59c9c8f202 ("tools: ynl: generate code for ovs families")
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions