netdev - Re: [QUERY] mctp: getsockopt unknown option return code -EINVAL

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: <048e6efc6e61901d0df3defaf6cc64c2afa5f937.camel@codeconstruct.com.au>
Date: Mon, 01 Sep 2025 15:24:31 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Alok Tiwari <alok.a.tiwari@...cle.com>, matt@...econstruct.com.au, 
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com,  horms@...nel.org, netdev@...r.kernel.org
Subject: Re: [QUERY] mctp: getsockopt unknown option return code -EINVAL

Hi Alok,

> Would it be ideal to return -ENOPROTOOPT instead of -EINVAL in
> mctp_getsockopt() when an option is unrecognized?
> This would match the behavior of mctp_setsockopt() and follow the
> standard kernel socket API convention for unknown options.

Yes, I think this makes sense, and probably extended to the level !=
SOL_MCTP checks too.

Is there a particular path you're looking at here?

Cheers,


Jeremy