From: Andrew Morton <akpm@linux-foundation.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Balbir Singh <bsingharora@gmail.com>,
Yang Yang <yang.yang29@zte.com.cn>,
Wang Yaxin <wang.yaxin@zte.com.cn>, Arnd Bergmann <arnd@arndb.de>,
xu xin <xu.xin16@zte.com.cn>, Kun Jiang <jiang.kun2@zte.com.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] delayacct: fix uapi timespec64 definition
Date: Mon, 2 Feb 2026 12:37:54 -0800 [thread overview]
Message-ID: <20260202123754.1bf674cd3b58ce0cb2cfa006@linux-foundation.org> (raw)
In-Reply-To: <20260202095906.1344100-1-arnd@kernel.org>
On Mon, 2 Feb 2026 10:59:00 +0100 Arnd Bergmann <arnd@kernel.org> wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> 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.
>
Thanks.
> @@ -251,14 +242,14 @@ struct taskstats {
> __u64 irq_delay_min;
>
> /*v17: delay max timestamp record*/
> - struct timespec64 cpu_delay_max_ts;
> - struct timespec64 blkio_delay_max_ts;
> - struct timespec64 swapin_delay_max_ts;
> - struct timespec64 freepages_delay_max_ts;
> - struct timespec64 thrashing_delay_max_ts;
> - struct timespec64 compact_delay_max_ts;
> - struct timespec64 wpcopy_delay_max_ts;
> - struct timespec64 irq_delay_max_ts;
> + struct __kernel_timespec cpu_delay_max_ts;
> + struct __kernel_timespec blkio_delay_max_ts;
> + struct __kernel_timespec swapin_delay_max_ts;
> + struct __kernel_timespec freepages_delay_max_ts;
> + struct __kernel_timespec thrashing_delay_max_ts;
> + struct __kernel_timespec compact_delay_max_ts;
> + struct __kernel_timespec wpcopy_delay_max_ts;
> + struct __kernel_timespec irq_delay_max_ts;
> } __uapi_arch_align;
There's no __uapi_arch_align here in any tree I looked at?
next prev parent reply other threads:[~2026-02-02 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:59 Arnd Bergmann
2026-02-02 13:08 ` wang.yaxin
2026-02-02 20:37 ` Andrew Morton [this message]
2026-02-02 20:47 ` Arnd Bergmann
2026-02-13 8:44 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260202123754.1bf674cd3b58ce0cb2cfa006@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bsingharora@gmail.com \
--cc=jiang.kun2@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=wang.yaxin@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®