From: Arnd Bergmann <arnd@kernel.org>
To: Balbir Singh <bsingharora@gmail.com>,
Yang Yang <yang.yang29@zte.com.cn>,
Wang Yaxin <wang.yaxin@zte.com.cn>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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: [PATCH] delayacct: fix uapi timespec64 definition
Date: Mon, 2 Feb 2026 10:59:00 +0100 [thread overview]
Message-ID: <20260202095906.1344100-1-arnd@kernel.org> (raw)
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.
Fixes: 29b63f6eff0e ("delayacct: add timestamp of delay max")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
include/uapi/linux/taskstats.h | 27 +++++++++------------------
kernel/delayacct.c | 6 ++++--
2 files changed, 13 insertions(+), 20 deletions(-)
diff --git a/include/uapi/linux/taskstats.h b/include/uapi/linux/taskstats.h
index a66b2d84a310..cc7fccd57979 100644
--- a/include/uapi/linux/taskstats.h
+++ b/include/uapi/linux/taskstats.h
@@ -18,16 +18,7 @@
#define _LINUX_TASKSTATS_H
#include <linux/types.h>
-#ifdef __KERNEL__
-#include <linux/time64.h>
-#else
-#ifndef _LINUX_TIME64_H
-struct timespec64 {
- __s64 tv_sec; /* seconds */
- long tv_nsec; /* nanoseconds */
-};
-#endif
-#endif
+#include <linux/time_types.h>
/* Format for per-task data returned to userland when
* - a task exits
@@ -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;
diff --git a/kernel/delayacct.c b/kernel/delayacct.c
index d58ffc63bcba..2e55c493c98b 100644
--- a/kernel/delayacct.c
+++ b/kernel/delayacct.c
@@ -18,7 +18,8 @@
do { \
d->type##_delay_max = tsk->delays->type##_delay_max; \
d->type##_delay_min = tsk->delays->type##_delay_min; \
- d->type##_delay_max_ts = tsk->delays->type##_delay_max_ts; \
+ d->type##_delay_max_ts.tv_sec = tsk->delays->type##_delay_max_ts.tv_sec; \
+ d->type##_delay_max_ts.tv_nsec = tsk->delays->type##_delay_max_ts.tv_nsec; \
tmp = d->type##_delay_total + tsk->delays->type##_delay; \
d->type##_delay_total = (tmp < d->type##_delay_total) ? 0 : tmp; \
d->type##_count += tsk->delays->type##_count; \
@@ -175,7 +176,8 @@ int delayacct_add_tsk(struct taskstats *d, struct task_struct *tsk)
d->cpu_delay_max = tsk->sched_info.max_run_delay;
d->cpu_delay_min = tsk->sched_info.min_run_delay;
- d->cpu_delay_max_ts = tsk->sched_info.max_run_delay_ts;
+ d->cpu_delay_max_ts.tv_sec = tsk->sched_info.max_run_delay_ts.tv_sec;
+ d->cpu_delay_max_ts.tv_nsec = tsk->sched_info.max_run_delay_ts.tv_nsec;
tmp = (s64)d->cpu_delay_total + t2;
d->cpu_delay_total = (tmp < (s64)d->cpu_delay_total) ? 0 : tmp;
tmp = (s64)d->cpu_run_virtual_total + t3;
--
2.39.5
next reply other threads:[~2026-02-02 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:59 Arnd Bergmann [this message]
2026-02-02 13:08 ` wang.yaxin
2026-02-02 20:37 ` Andrew Morton
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=20260202095906.1344100-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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®