linux-kernel - Re: [PATCH] kselftest/arm64: Use syscall() macro over nolibc my

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: <aWz5VDoGPiOrfsTN@sirena.co.uk>
Date: Sun, 18 Jan 2026 15:16:36 +0000
From: Mark Brown <broonie@...nel.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will@...nel.org>, Shuah Khan <shuah@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Use syscall() macro over nolibc
 my_syscall()

On Sat, Jan 17, 2026 at 01:10:51PM +0100, Thomas Weißschuh wrote:
> The my_syscall*() macros are internal implementation details of nolibc.
> Nolibc also provides the regular syscall(2), which is also a macro
> and directly expands to the correct my_syscall().
> 
> Use syscall() instead.
> 
> As a side-effect this fixes some return value checks, as my_syscall()
> returns the raw value as set by the kernel and does not set errno.

Acked-by: Mark Brown <broonie@...nel.org>

Looking at the history the nolibc syscall() was added after we started
doing this in the arm64 selftests, it was 2023 while the tpidr2 test
is from 2022.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)