Re: kernel/fork.c:3088:2: warning: clone3() entry point is missing, please fix

Hi Arnd,

On Mon, 2025-06-30 at 12:02 +0200, Arnd Bergmann wrote:
> Some architectures have custom calling conventions for the
> fork/vfork/clone/clone3 syscalls, e.g. to handle copying all the
> registers correctly when the normal syscall entry doesn't do that,
> or to handle the changing stack correctly.
> 
> I see that both sparc and hexagon have a custom clone() syscall,
> so they likely need a custom clone3() as well, while sh and
> nios2 probably don't.
> 
> All four would need a custom assembler implementation in userspace
> for each libc, in order to test the userspace calling the clone3()
> function. For testing the kernel entry point itself, see Christian's
> original test case[1].

Thanks for the explanation. So, I guess as long as a proposed implementation
of clone3() on sh would pass Arnd's test program, it should be good for merging?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913