diff options
author | Lukasz Majewski <lukma@denx.de> | 2020-02-06 13:25:35 +0100 |
---|---|---|
committer | Lukasz Majewski <lukma@denx.de> | 2020-03-03 14:28:08 +0100 |
commit | 66449d93393dabbfcf33c045c1d3cb49e77a25e4 (patch) | |
tree | 390e7c1e6f473808bb6ec9ef490be0883d5576da /sysdeps/alpha/Makefile | |
parent | d962a5d68a140811eb4b6cf788c41ff471fd95b4 (diff) | |
download | glibc-66449d93393dabbfcf33c045c1d3cb49e77a25e4.tar.gz glibc-66449d93393dabbfcf33c045c1d3cb49e77a25e4.tar.xz glibc-66449d93393dabbfcf33c045c1d3cb49e77a25e4.zip |
y2038: linux: Provide __utime64 implementation
This patch replaces auto generated wrapper (as described in sysdeps/unix/sysv/linux/syscalls.list) for utime with one which adds extra support for setting file's access and modification 64 bit time on machines with __TIMESIZE != 64. Internally, the __utimensat_time64 helper function is used. This patch is necessary for having architectures with __WORDSIZE == 32 && __TIMESIZE != 64 Y2038 safe. Moreover, a 32 bit version - __utime has been refactored to internally use __utime64. The __utime is now supposed to be used on systems still supporting 32 bit time (__TIMESIZE != 64) - hence the necessary conversion between struct utimbuf and struct __utimbuf64. 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 proper usage of both __utime64 and __utime. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'sysdeps/alpha/Makefile')
0 files changed, 0 insertions, 0 deletions