[PATCH v2] manual: describe syscall numbers not supported via syscall()

Yury Khrustalev yury.khrustalev@arm.com
Tue Sep 16 12:33:27 GMT 2025


Carlos, my apologies, I think I've sent it to a wrong address.

On Tue, Sep 16, 2025 at 10:00:16AM +0100, Yury Khrustalev wrote:
> The syscall() function allows to make system calls directly, however,
> in the case of system calls that affect internal state of process or
> thread, the caller would have to take care of extensive setup necessary
> for the internals of Glibc to work correctly in the child threads. This
> may make using syscall() with these syscall numbers impractical and
> prone to undefined behaviour.
> 
> ---
> 
> This need for this patch was discussed in
> https://patchwork.sourceware.org/project/glibc/patch/20250901095112.1672473-3-yury.khrustalev@arm.com/
> 
> v1: https://patchwork.sourceware.org/project/glibc/list/?series=51954
> 
> base-commit: 13d67746cb
> 
> ...

Thanks,
Yury



More information about the Libc-alpha mailing list