netdev - Re: [RFC] netlink: add variable-length / auto integers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231011132107.7eb89258@kernel.org>
Date: Wed, 11 Oct 2023 13:21:07 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, nicolas.dichtel@...nd.com,
 johannes@...solutions.net, fw@...len.de, pablo@...filter.org,
 mkubecek@...e.cz, aleksander.lobakin@...el.com
Subject: Re: [RFC] netlink: add variable-length / auto integers

On Wed, 11 Oct 2023 19:01:53 +0200 Jiri Pirko wrote:
> Wed, Oct 11, 2023 at 06:16:24PM CEST, kuba@...nel.org wrote:
> >No, fixed types are still allowed, just discouraged.  
> 
> Why?

The only legit use case that comes to mind is protocol
fields which have strictly-defined size. People like
to mirror their size into netlink, for better or worse.

> Is there goint to be warn in ynl gen?

Just a comment in the docs:

https://lore.kernel.org/all/20231011090859.3fc30812@kernel.org/