aboutsummaryrefslogtreecommitdiff
path: root/conform/data
diff options
context:
space:
mode:
authorLukasz Majewski <lukma@denx.de>2019-10-24 12:12:16 +0200
committerLukasz Majewski <lukma@denx.de>2019-11-02 08:41:25 +0100
commitf5b6fd258b6dd520403a20024e58cb491aca4cbd (patch)
tree4fab7e7f8adb97d6619f8080afbcb66101a9f533 /conform/data
parent7aeab82edb38390c2a02519d312e098f4049e867 (diff)
downloadglibc-f5b6fd258b6dd520403a20024e58cb491aca4cbd.tar
glibc-f5b6fd258b6dd520403a20024e58cb491aca4cbd.tar.gz
glibc-f5b6fd258b6dd520403a20024e58cb491aca4cbd.tar.bz2
glibc-f5b6fd258b6dd520403a20024e58cb491aca4cbd.zip
y2038: linux: Provide __utimensat64 implementation
This patch provides new __utimensat64 explicit 64 bit function for setting access and modification time of a file. Moreover, a 32 bit version - __utimensat has been refactored to internally use __utimensat64. The __utimensat is now supposed to be used on systems still supporting 32 bit time (__TIMESIZE != 64) - hence the necessary conversions to 64 bit struct __timespec64. When pointer to struct __timespec64 is NULL - the file access and modification time is set to the current one and no conversions from struct timespec to __timespec64 are performed. The new utimensat_time64 syscall available from Linux 5.1+ has been used, when applicable. The new helper function - __utimensat64_helper - has been introduced to facilitate code re-usage on function providing futimens syscall handling. The Linux kernel checks if passed tv_nsec value overflows, so there is no need to repeat it in glibc. When utimensat syscall on systems supporting 32 bit time ABI is used, the check is performed if passed data (which may have 64 bit tv_sec) fits into 32 bit range. Build tests: - The code has been tested on x86_64/x86 (native compilation): make PARALLELMFLAGS="-j8" && make xcheck PARALLELMFLAGS="-j8" - The glibc has been build tested (make PARALLELMFLAGS="-j8") for x86 (i386), x86_64-x32, and armv7 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 - Use of cross-test-ssh.sh for ARM (armv7): make PARALLELMFLAGS="-j8" test-wrapper='./cross-test-ssh.sh root@192.168.7.2' xcheck Linux kernel, headers and minimal kernel version for glibc build test matrix: - Linux v5.1 (with utimensat_time64) and glibc build with v5.1 as minimal kernel version (--enable-kernel="5.1.0") The __ASSUME_TIME64_SYSCALLS flag defined. - Linux v5.1 and default minimal kernel version The __ASSUME_TIME64_SYSCALLS not defined, but kernel supports utimensat_time64 syscall. - Linux v4.19 (no utimensat_time64 support) with default minimal kernel version for contemporary glibc This kernel doesn't support utimensat_time64 syscall, so the fallback to utimensat is tested. The above tests were performed with Y2038 redirection applied as well as without (so the __TIMESIZE != 64 execution path is checked as well). No regressions were observed.
Diffstat (limited to 'conform/data')
0 files changed, 0 insertions, 0 deletions