diff options
| author | 2025-11-05 18:32:12 +0000 | |
|---|---|---|
| committer | 2025-11-18 18:08:03 +0100 | |
| commit | fbd8c752a8e3d00341fa7754d6e45e60d6b45490 (patch) | |
| tree | 358a08118beaba8bfad201b686c2cc1f1999d4f4 /drivers/net/wireguard/netlink.c | |
| parent | Merge branch 'gve-implement-xdp-hw-rx-timestamping-support-for-dq' (diff) | |
| download | wireguard-linux-devel.tar.xz wireguard-linux-devel.zip | |
wireguard: netlink: enable strict genetlink validationdevel
WireGuard is a modern enough genetlink family, that it doesn't need
resv_start_op. It already had policies in place when it was first
merged, it has also never used the reserved field, or other things
toggled by resv_start_op.
wireguard-tools have always used zero initialized memory, and have never
touched the reserved field, neither have any other clients I have
checked. Closed-source clients are much more likely to use the
embeddedable library from wireguard-tools, than a DIY implementation
using uninitialized memory.
Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to '')
| -rw-r--r-- | drivers/net/wireguard/netlink.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/net/wireguard/netlink.c b/drivers/net/wireguard/netlink.c index 67f962eb8b46..8adeec6f9440 100644 --- a/drivers/net/wireguard/netlink.c +++ b/drivers/net/wireguard/netlink.c @@ -631,7 +631,6 @@ static const struct genl_ops genl_ops[] = { static struct genl_family genl_family __ro_after_init = { .ops = genl_ops, .n_ops = ARRAY_SIZE(genl_ops), - .resv_start_op = WG_CMD_SET_DEVICE + 1, .name = WG_GENL_NAME, .version = WG_GENL_VERSION, .maxattr = WGDEVICE_A_MAX, |
