diff options
| author | maminjie <maminjie2@huawei.com> | 2021-12-20 19:36:32 +0800 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-12-21 09:47:16 -0300 |
| commit | e0fc721ce600038dd390e77cfe52440707ef574d (patch) | |
| tree | a73e91be713e1e136975e165f3896d80a8e8c3c6 /sysdeps/unix | |
| parent | de8a0897e3c084dc93676e331b610f146000a0ab (diff) | |
| download | glibc-e0fc721ce600038dd390e77cfe52440707ef574d.tar.gz glibc-e0fc721ce600038dd390e77cfe52440707ef574d.tar.xz glibc-e0fc721ce600038dd390e77cfe52440707ef574d.zip | |
Linux: Fix 32-bit vDSO for clock_gettime on powerpc32
When the clock_id is CLOCK_PROCESS_CPUTIME_ID or CLOCK_THREAD_CPUTIME_ID, on the 5.10 kernel powerpc 32-bit, the 32-bit vDSO is executed successfully ( because the __kernel_clock_gettime in arch/powerpc/kernel/vdso32/gettimeofday.S does not support these two IDs, the 32-bit time_t syscall will be used), but tp32.tv_sec is equal to 0, causing the 64-bit time_t syscall to continue to be used, resulting in two system calls. Fix commit 72e84d1db22203e01a43268de71ea8669eca2863. Signed-off-by: maminjie <maminjie2@huawei.com> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'sysdeps/unix')
| -rw-r--r-- | sysdeps/unix/sysv/linux/clock_gettime.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sysdeps/unix/sysv/linux/clock_gettime.c b/sysdeps/unix/sysv/linux/clock_gettime.c index 91df6b3d96..9c7d907325 100644 --- a/sysdeps/unix/sysv/linux/clock_gettime.c +++ b/sysdeps/unix/sysv/linux/clock_gettime.c @@ -53,7 +53,7 @@ __clock_gettime64 (clockid_t clock_id, struct __timespec64 *tp) { struct timespec tp32; r = INTERNAL_VSYSCALL_CALL (vdso_time, 2, clock_id, &tp32); - if (r == 0 && tp32.tv_sec > 0) + if (r == 0 && tp32.tv_sec >= 0) { *tp = valid_timespec_to_timespec64 (tp32); return 0; |