netdev - Re: [PATCH net] uapi: ioam6: adjust the maximum size of a schema

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: <59f897f8-4358-418d-a6ed-d422bb6d7cb4@uliege.be>
Date: Sat, 22 Nov 2025 11:18:13 +0100
From: Justin Iurman <justin.iurman@...ege.be>
To: David Ahern <dsahern@...nel.org>, davem@...emloft.net
Cc: netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net] uapi: ioam6: adjust the maximum size of a schema

On 11/21/25 20:18, David Ahern wrote:
> On 11/21/25 11:55 AM, Justin Iurman wrote:
>>
>> You're right, it might be too risky. Besides, the current code (i.e.,
>> IOAM6_MAX_SCHEMA_DATA_LEN=1020) doesn't break anything per se, it was
>> mainly for convenience. Do you think it would be OK to introduce a new
>> constant in the uapi, as suggested above? Or did your comment also apply
>> to that part?
> 
> You cannot break any existing implementation which means kernel side you
> have to allow the current DATA_LEN. Given that there is little point in
> trying to change it now. If the spec has a 240B limit, you could return
> a warning message telling users when they exceed it. UAPI wise I think
> we are stuck with what exists.

That's what I suspected and feared. Anyway, as I said, this change was 
purely for convenience, so no big deal. I think this is a good idea to 
return a warning to users, thanks! I'll submit that to net-next.