summaryrefslogtreecommitdiff
path: root/fs/utimes.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2018-04-17 09:11:58 +0200
committerArnd Bergmann <arnd@arndb.de>2018-08-29 15:42:22 +0200
commita4f7a3004630f1a0fb130ab1824942a49ce33140 (patch)
treea0012351b8ea2637c78e0e0e2fc0a914a6a9bac0 /fs/utimes.c
parentc5ba7e6c9ba545c3f67188de510d4cab2e3223b2 (diff)
downloadlwn-a4f7a3004630f1a0fb130ab1824942a49ce33140.tar.gz
lwn-a4f7a3004630f1a0fb130ab1824942a49ce33140.zip
y2038: Change sys_utimensat() to use __kernel_timespec
When 32-bit architectures get changed to support 64-bit time_t, utimensat() needs to use the new __kernel_timespec structure as its argument. The older utime(), utimes() and futimesat() system calls don't need a corresponding change as they are no longer used on C libraries that have 64-bit time support. As we do for the other syscalls that have timespec arguments, we reuse the 'compat' syscall entry points to implement the traditional four interfaces, and only leave the new utimensat() as a native handler, so that the same code gets used on both 32-bit and 64-bit kernels on each syscall. Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'fs/utimes.c')
-rw-r--r--fs/utimes.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/utimes.c b/fs/utimes.c
index 79a65c163f40..d30f409ecc1a 100644
--- a/fs/utimes.c
+++ b/fs/utimes.c
@@ -166,7 +166,7 @@ out:
}
SYSCALL_DEFINE4(utimensat, int, dfd, const char __user *, filename,
- struct timespec __user *, utimes, int, flags)
+ struct __kernel_timespec __user *, utimes, int, flags)
{
struct timespec64 tstimes[2];