[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <96db85326505785727bcfe45b99ae12fdbfb548a.camel@sipsolutions.net>
Date: Mon, 08 Sep 2025 09:55:31 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Asbjørn Sloth Tønnesen
<ast@...erby.net>, "Keller, Jacob E" <jacob.e.keller@...el.com>, "Jason A.
Donenfeld" <Jason@...c4.com>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
Abeni <pabeni@...hat.com>
Cc: Donald Hunter <donald.hunter@...il.com>, Simon Horman
<horms@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
"wireguard@...ts.zx2c4.com" <wireguard@...ts.zx2c4.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 06/11] tools: ynl-gen: don't validate nested
array attribute types
On Sat, 2025-09-06 at 15:10 +0000, Asbjørn Sloth Tønnesen wrote:
>
> For the other families, I don't know how well defined it is, Johannes have
> stated that nl80211 doesn't care which types are used, but I have no idea
> how consistent clients have abused that statement to send random data,
> or do they all just send zeros?
I think most clients probably send incrementing numbers (1, 2, 3, ...),
but maybe some start at 0, some sometimes might use band numbers and
thus have sparse values, etc.
But as I just wrote, I'm not really sure it should be used at all.
joahnnes
Powered by blists - more mailing lists