summary refs log tree commit diff
path: root/nptl/pthread_cond_wait.c
diff options
context:
space:
mode:
authorLukasz Majewski <lukma@denx.de>2020-04-21 20:56:24 +0200
committerLukasz Majewski <lukma@denx.de>2020-05-20 01:03:26 +0200
commit0308077e3a4ff1c123cdddd311f55a2ecdd3115c (patch)
treef0a13fb5849bbbac16081ed421436bfea4f81797 /nptl/pthread_cond_wait.c
parent8f8a6cae487beb7af465fd42fba892eee5e0c319 (diff)
downloadglibc-0308077e3a4ff1c123cdddd311f55a2ecdd3115c.tar.gz
glibc-0308077e3a4ff1c123cdddd311f55a2ecdd3115c.tar.xz
glibc-0308077e3a4ff1c123cdddd311f55a2ecdd3115c.zip
y2038: linux: Provide __adjtime64 implementation
This patch provides new __adjtime64 explicit 64 bit function for adjusting
Linux kernel clock.

Internally, the __clock_adjtime64 syscall is used instead of __adjtimex. This
patch is necessary for having architectures with __WORDSIZE == 32 Y2038 safe.

Moreover, a 32 bit version - __adjtime has been refactored to internally use
__adjtime64.

The __adjtime is now supposed to be used on systems still supporting 32
bit time (__TIMESIZE != 64) - hence the necessary conversions between struct
timeval and 64 bit struct __timeval64.

Build tests:
./src/scripts/build-many-glibcs.py glibcs

Run-time tests:
- Run specific tests on ARM/x86 32bit systems (qemu):
  https://github.com/lmajewski/meta-y2038 and run tests:
  https://github.com/lmajewski/y2038-tests/commits/master

Above tests were performed with Y2038 redirection applied as well as without to
test the proper usage of both __adjtime64 and __adjtime.

Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
Diffstat (limited to 'nptl/pthread_cond_wait.c')
0 files changed, 0 insertions, 0 deletions