netdev - Re: [RFC net-next 00/14] wireguard: netlink: ynl conversion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHmME9ra4_P0-FdVV75gaAWiW8yWsUJJsmTes_kac0EdTgnjHQ@mail.gmail.com>
Date: Tue, 16 Sep 2025 17:51:21 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Asbjørn Sloth Tønnesen <ast@...erby.net>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, 
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Donald Hunter <donald.hunter@...il.com>, Simon Horman <horms@...nel.org>, 
	Jacob Keller <jacob.e.keller@...el.com>, Andrew Lunn <andrew+netdev@...n.ch>, 
	wireguard@...ts.zx2c4.com, netdev@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next 00/14] wireguard: netlink: ynl conversion

Hi Asbjorn,

On Fri, Sep 5, 2025 at 12:03 AM Asbjørn Sloth Tønnesen <ast@...erby.net> wrote:
>
> This series contains the wireguard changes needed to adopt
> an YNL-based generated netlink code.
>
> This RFC series is posted for reference, as it is referenced
> from the current v1 series of ynl preparations, which has to
> go in before this series can be submitted for net-next.

I'm not actually convinced this makes anything better. It seems like
the code becomes more complicated and less obvious. What is the
benefit here? As is, I really don't like this direction.

Jason