netdev - Re: [PATCH net-next v2 2/2] tools: ynl: rework the string representation of NlError

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: <20251028163454.66ca7dc3@kernel.org>
Date: Tue, 28 Oct 2025 16:34:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
 donald.hunter@...il.com, ast@...erby.net
Subject: Re: [PATCH net-next v2 2/2] tools: ynl: rework the string
 representation of NlError

On Tue, 28 Oct 2025 14:58:59 +0100 Andrew Lunn wrote:
> I think as a kernel programmer, i would prefer EINVAL over Invalid
> argument. If i'm going to be digging into the kernel sources to find
> where the error is happening, it is one less translation i need to
> make.
> 
> >>> print(errno.errorcode[1])  
> EPERM
> >>> print(errno.errorcode[2])  
> ENOENT
> >>> print(errno.errorcode[110])  
> ETIMEDOUT
> 
> I suppose the question is, who is the intended user of ynl? Do we want
> user friendly messages, or kernel developer friendly messages?

A mix of both, it is packaged in distros.