public inbox for wireguard@lists.zx2c4.com
 help / color / mirror / Atom feed
From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
	"Donald Hunter" <donald.hunter@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	"Jacob Keller" <jacob.e.keller@intel.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH net-next v1 03/11] wireguard: netlink: enable strict genetlink validation
Date: Wed, 29 Oct 2025 20:51:11 +0000	[thread overview]
Message-ID: <20251029205123.286115-4-ast@fiberby.net> (raw)
In-Reply-To: <20251029205123.286115-1-ast@fiberby.net>

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>
---
 drivers/net/wireguard/netlink.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/net/wireguard/netlink.c b/drivers/net/wireguard/netlink.c
index d36e94220d2c3..024d4a6cc74c6 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,
-- 
2.51.0


  parent reply	other threads:[~2025-11-19 17:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 20:51 [PATCH net-next v1 00/11] wireguard: netlink: ynl conversion Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 01/11] wireguard: netlink: validate nested arrays in policy Asbjørn Sloth Tønnesen
2025-10-30  9:46   ` Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 02/11] wireguard: netlink: use WG_KEY_LEN in policies Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` Asbjørn Sloth Tønnesen [this message]
2025-10-29 20:51 ` [PATCH net-next v1 04/11] netlink: specs: add specification for wireguard Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 05/11] uapi: wireguard: move enum wg_cmd Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 06/11] uapi: wireguard: move flag enums Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 07/11] uapi: wireguard: generate header with ynl-gen Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 08/11] tools: ynl: add sample for wireguard Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 09/11] wireguard: netlink: convert to split ops Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 10/11] wireguard: netlink: rename netlink handlers Asbjørn Sloth Tønnesen
2025-10-29 20:51 ` [PATCH net-next v1 11/11] wireguard: netlink: generate netlink code Asbjørn Sloth Tønnesen

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=20251029205123.286115-4-ast@fiberby.net \
    --to=ast@fiberby.net \
    --cc=Jason@zx2c4.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wireguard@lists.zx2c4.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