netdev - Re: [PATCH WITHDRAWN] net: ynl: return actual error code in ynl_exec

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: <tencent_88053624249C81B35E3F59FCF6F53DEA4007@qq.com>
Date: Tue, 30 Sep 2025 20:39:33 +0800
From: Haofeng Li <920484857@...com>
To: kuba@...nel.org
Cc: 13266079573@....com,
	920484857@...com,
	donald.hunter@...il.com,
	lihaofeng@...inos.cn,
	linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH WITHDRAWN] net: ynl: return actual error code in ynl_exec_dump()

> This is not kernel code the error is always -1, and the details are in errno.

Thank you for the feedback and for pointing that out.

You are absolutely right. I now understand that in the context of this 
userspace code, the error handling convention relies on errno for 
details when the return value is -1. My patch was attempting to align 
the return value with a specific internal error code, which, as you clarified,
 is not the established practice here and doesn't provide the intended 
benefit in this case.

I appreciate you taking the time to explain this.