diff options
author | Arnd Bergmann <arnd@arndb.de> | 2018-04-17 09:11:58 +0200 |
---|---|---|
committer | Arnd Bergmann <arnd@arndb.de> | 2018-08-29 15:42:23 +0200 |
commit | 185cfaf7641e14af85635bb2750da302e32b04e3 (patch) | |
tree | 2c9be980c5bef6c442529df090e5f5170196b4ce /lib/irq_poll.c | |
parent | a4f7a3004630f1a0fb130ab1824942a49ce33140 (diff) | |
download | linux-185cfaf7641e14af85635bb2750da302e32b04e3.tar.gz linux-185cfaf7641e14af85635bb2750da302e32b04e3.tar.bz2 linux-185cfaf7641e14af85635bb2750da302e32b04e3.zip |
y2038: Compile utimes()/futimesat() conditionally
There are four generations of utimes() syscalls: utime(), utimes(),
futimesat() and utimensat(), each one being a superset of the previous
one. For y2038 support, we have to add another one, which is the same
as the existing utimensat() but always passes 64-bit times_t based
timespec values.
There are currently 10 architectures that only use utimensat(), two
that use utimes(), futimesat() and utimensat() but not utime(), and 11
architectures that have all four, and those define __ARCH_WANT_SYS_UTIME
in order to get a sys_utime implementation. Since all the new
architectures only want utimensat(), moving all the legacy entry points
into a common __ARCH_WANT_SYS_UTIME guard simplifies the logic. Only alpha
and ia64 grow a tiny bit as they now also get an unused sys_utime(),
but it didn't seem worth the extra complexity of adding yet another
ifdef for those.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'lib/irq_poll.c')
0 files changed, 0 insertions, 0 deletions