[PATCH] manual: describe unsupported SYS_clone{3} when used via syscall

[H. Peter Anvin]

On 2025-09-12 01:29, Yury Khrustalev wrote:
> The syscall() function allows to make system calls directly, however
> in the case of SYS_clone and SYS_clone3 the caller would have to take
> care of extensive setup necessary for the internals of Glibc to work
> correctly in the child threads which may make using syscall() with
> these syscall numbers impractical.
> 
> ---
> This need for this patch was discussed in
> https://inbox.sourceware.org/libc-alpha/20250901095112.1672473-3-yury.khrustalev@arm.com/
> 
> base-commit: cae3c9e3a1

If you are going to make such an enumeration, you should add clone2
(which some platforms have), vfork, sigreturn, and rt_sigreturn as well
at a minimum.

All of them require very special handling of the stack.

	-hpa