diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2019-10-25 22:46:48 +0200 |
|---|---|---|
| committer | Arnd Bergmann <arnd@arndb.de> | 2019-11-15 14:38:29 +0100 |
| commit | bdd565f817a74b9e30edec108f7cb1dbc762b8a6 (patch) | |
| tree | ce401e7b12bc0c3c77af23ba8e1fd18f223ee040 /kernel/sys.c | |
| parent | 2a785996cc5e2fc1d1d29d196f530905f68d2dc2 (diff) | |
| download | linux-bdd565f817a74b9e30edec108f7cb1dbc762b8a6.tar.gz linux-bdd565f817a74b9e30edec108f7cb1dbc762b8a6.tar.bz2 linux-bdd565f817a74b9e30edec108f7cb1dbc762b8a6.zip | |
y2038: rusage: use __kernel_old_timeval
There are two 'struct timeval' fields in 'struct rusage'.
Unfortunately the definition of timeval is now ambiguous when used in
user space with a libc that has a 64-bit time_t, and this also changes
the 'rusage' definition in user space in a way that is incompatible with
the system call interface.
While there is no good solution to avoid all ambiguity here, change
the definition in the kernel headers to be compatible with the kernel
ABI, using __kernel_old_timeval as an unambiguous base type.
In previous discussions, there was also a plan to add a replacement
for rusage based on 64-bit timestamps and nanosecond resolution,
i.e. 'struct __kernel_timespec'. I have patches for that as well,
if anyone thinks we should do that.
Reviewed-by: Cyrill Gorcunov <gorcunov@gmail.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'kernel/sys.c')
| -rw-r--r-- | kernel/sys.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/kernel/sys.c b/kernel/sys.c index a611d1d58c7d..d3aef31e24dc 100644 --- a/kernel/sys.c +++ b/kernel/sys.c @@ -1763,8 +1763,8 @@ void getrusage(struct task_struct *p, int who, struct rusage *r) unlock_task_sighand(p, &flags); out: - r->ru_utime = ns_to_timeval(utime); - r->ru_stime = ns_to_timeval(stime); + r->ru_utime = ns_to_kernel_old_timeval(utime); + r->ru_stime = ns_to_kernel_old_timeval(stime); if (who != RUSAGE_CHILDREN) { struct mm_struct *mm = get_task_mm(p); |