Skip to content

Commit 0f26922

Browse files
prime-zengKAGA-KOKO
authored andcommitted
cputime: Prevent 32bit overflow in time[val|spec]_to_cputime()
The datatype __kernel_time_t is u32 on 32bit platform, so its subject to overflows in the timeval/timespec to cputime conversion. Currently the following functions are affected: 1. setitimer() 2. timer_create/timer_settime() 3. sys_clock_nanosleep This can happen on MIPS32 and ARM32 with "Full dynticks CPU time accounting" enabled, which is required for CONFIG_NO_HZ_FULL. Enforce u64 conversion to prevent the overflow. Fixes: 31c1fc8 ("ARM: Kconfig: allow full nohz CPU accounting") Signed-off-by: zengtao <prime.zeng@huawei.com> Reviewed-by: Arnd Bergmann <arnd@arndb.de> Cc: <fweisbec@gmail.com> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/1454384314-154784-1-git-send-email-prime.zeng@huawei.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
1 parent 36f90b0 commit 0f26922

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

include/asm-generic/cputime_nsecs.h

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ typedef u64 __nocast cputime64_t;
7575
*/
7676
static inline cputime_t timespec_to_cputime(const struct timespec *val)
7777
{
78-
u64 ret = val->tv_sec * NSEC_PER_SEC + val->tv_nsec;
78+
u64 ret = (u64)val->tv_sec * NSEC_PER_SEC + val->tv_nsec;
7979
return (__force cputime_t) ret;
8080
}
8181
static inline void cputime_to_timespec(const cputime_t ct, struct timespec *val)
@@ -91,7 +91,8 @@ static inline void cputime_to_timespec(const cputime_t ct, struct timespec *val)
9191
*/
9292
static inline cputime_t timeval_to_cputime(const struct timeval *val)
9393
{
94-
u64 ret = val->tv_sec * NSEC_PER_SEC + val->tv_usec * NSEC_PER_USEC;
94+
u64 ret = (u64)val->tv_sec * NSEC_PER_SEC +
95+
val->tv_usec * NSEC_PER_USEC;
9596
return (__force cputime_t) ret;
9697
}
9798
static inline void cputime_to_timeval(const cputime_t ct, struct timeval *val)

0 commit comments

Comments
 (0)