linux-kernel - Re: [PATCH 2/3] sparc: Add architecture support for clone3

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: <b7801647-9149-4068-9627-8346ad822908@gaisler.com>
Date: Mon, 19 Jan 2026 13:39:10 +0100
From: Ludwig Rydberg <ludwig.rydberg@...sler.com>
To: Jessica Clarke <jrtc27@...c27.com>
Cc: davem@...emloft.net, andreas@...sler.com, brauner@...nel.org,
 shuah@...nel.org, sparclinux@...r.kernel.org,
 linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
 arnd@...db.de, glaubitz@...sik.fu-berlin.de, geert@...ux-m68k.org,
 schuster.simon@...mens-energy.com
Subject: Re: [PATCH 2/3] sparc: Add architecture support for clone3

Hi Jessica,

> One of the benefits of having a new clone3 is that the interface can be
> made the same across all architectures*, unlike clone, which both passes
> the arguments in different orders for different architectures and, in
> the case of SPARC, has this weird return convention inherited from the
> SunOS syscall interface. Is there a good reason to deviate for clone3
> too and keep this annoying oddity going, that requires special-casing
> SPARC when other architectures can just syscall(__NR_clone3, ...)?
> 

Thanks for commenting on this. No, you're right (there is no good reason).
The original implementation just followed how things were but I have a v2
coming up which will follow the regular kernel return value conventions.
This will ensure that syscall(__NR_clone3, ...) works on SPARC exactly
as it does on other architectures (i.e I'll drop the third patch in the
series).

Best regards,
// Ludwig