Re: [PATCH] delayacct: fix uapi timespec64 definition

From: Geert Uytterhoeven

Date: Fri Feb 13 2026 - 03:44:44 EST


On Mon, 2 Feb 2026 at 11:05, Arnd Bergmann <arnd@xxxxxxxxxx> wrote:
> From: Arnd Bergmann <arnd@xxxxxxxx>
>
> The custom definition of 'struct timespec64' is incompatible with
> both the kernel's internal definition and the glibc type, at least
> on big-endian targets that have the tv_nsec field in a different
> place, and the definition clashes with any userspace that also
> defines a timespec64 structure.
>
> Running the header check with -Wpadding enabled produces this output
> that warns about the incorrect padding:
>
> usr/include/linux/taskstats.h:25:1: error: padding struct size to alignment boundary with 4 bytes [-Werror=padded]
>
> Remove the hack and instead use the regular __kernel_timespec
> type that is meant to be used in uapi definitions.
>
> Fixes: 29b63f6eff0e ("delayacct: add timestamp of delay max")

JFTR, this commit was rebased, and is now commit 503efe850c7463a1
("delayacct: add timestamp of delay max") upstream.
Fixes: 503efe850c7463a1 ("delayacct: add timestamp of delay max")

> Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx>

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds