linux-toradex.git/tools/include/nolibc/sys, branch master

selftests/nolibc: add static assertions around time types handling

2026-01-06T11:08:08+00:00

The nolibc system call wrappers expect the libc types to be compatible
to the kernel types.

Make sure these expectations hold at compile-time.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-14-c662992f75d7@weissschuh.net

tools/nolibc: remove time conversions

2026-01-06T11:08:06+00:00

Now that 'struct timespec' and 'struct __kernel_timespec' are
compatible, the conversions are not necessary anymore.
The same holds true for 'struct itimerspec' and 'struct
__kernel_itimerspec'.

Remove the conversions.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-11-c662992f75d7@weissschuh.net

tools/nolibc/select: avoid libgcc 64-bit multiplications

2026-01-04T09:29:02+00:00

timeval::tv_usec is going to be 64-bit wide even on 32-bit
architectures. As not all architectures support 64-bit multiplications
instructions, calls to libgcc (__multi3()) may be emitted by the
compiler which are not provided by nolibc.

As tv_usec and tv_nsec are guaranteed to always fit into an uint32_t,
perform a 32-bit multiplication instead.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-7-c662992f75d7@weissschuh.net

tools/nolibc/gettimeofday: avoid libgcc 64-bit divisions

2026-01-04T09:29:01+00:00

timespec::tv_nsec is going to be 64-bit wide even on 32-bit
architectures. As not all architectures support 64-bit division
instructions, calls to libgcc (__divdi3()) may be emitted by the
compiler which are not provided by nolibc.

As tv_nsec is guaranteed to always fit into an uint32_t, perform a
32-bit division instead.

Signed-off-by: Thomas Weißschuh 
Reviewed-by: Arnd Bergmann 
Acked-by: Willy Tarreau 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-6-c662992f75d7@weissschuh.net

tools/nolibc: prefer explicit 64-bit time-related system calls

2026-01-04T09:29:00+00:00

Make sure to always use the 64-bit safe system calls
in preparation for 64-bit time_t on 32-bit architectures.

Also prevent issues on kernels which disable CONFIG_COMPAT_32BIT_TIME
and therefore don't provide the 32-bit system calls anymore.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-5-c662992f75d7@weissschuh.net

tools/nolibc/time: drop invocation of gettimeofday system call

2026-01-04T09:28:59+00:00

This invocation uses libc types with a system call. While this works
now, upcoming changes to 'struct timeval' would require type
conversions. If types are converted anyways, the clock_gettime() based
fallback can be used everywhere, simplifying the code.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-4-c662992f75d7@weissschuh.net

tools/nolibc/select: drop non-pselect based implementations

2026-01-04T09:28:58+00:00

These implementations use the libc 'struct timeval' with system calls
which can lead to type mismatches. Currently this is fine, but will
break with upcoming changes to 'struct timeval'.

If the structure needs to be converted anyways, the implementations
based on pselect can be used for all architectures. This simplifies the
logic.

Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-3-c662992f75d7@weissschuh.net

tools/nolibc/poll: use kernel types for system call invocations

2026-01-04T09:28:57+00:00

The system calls expect 'struct __kernel_old_timespec'.
While currently 'struct __kernel_old_timespec' and 'struct timespec' are
compatible, this is confusing. Especially as future patches will change
the definition of 'struct timespec'.

Use the correct kernel type instead.

Suggested-by: Arnd Bergmann 
Link: https://lore.kernel.org/lkml/fbca1d3e-12e4-4c4e-8091-87464035fe39@app.fastmail.com/
Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau 
Reviewed-by: Arnd Bergmann 
Link: https://patch.msgid.link/20251220-nolibc-uapi-types-v3-1-c662992f75d7@weissschuh.net

tools/nolibc: add ptrace support

2026-01-04T09:28:44+00:00

Add ptrace support, as it will be useful in UML.

Signed-off-by: Benjamin Berg 
[Thomas: drop va_args usage and linux/uio.h inclusion]
Signed-off-by: Thomas Weißschuh

tools/nolibc: avoid using plain integer as NULL pointer

2025-11-09T20:29:57+00:00

While an integer zero is a valid NULL pointer as per the C standard,
sparse will complain about it.

Use explicit NULL pointers instead.

Reported-by: kernel test robot 
Closes: https://lore.kernel.org/r/202509261452.g5peaXCc-lkp@intel.com/
Signed-off-by: Thomas Weißschuh 
Acked-by: Willy Tarreau