linux-user: Use direct syscall for utimensat
The linux utimensat syscall differs in semantics from the libc function because the syscall combines the features of utimensat() and futimens(). Rather than trying to split these apart in order to call the two libc functions which then call the same underlying syscall, just always directly make the host syscall. This fixes bugs in some of the corner cases which should return errors from the syscall but which we were incorrectly directing to futimens(). This doesn't reduce the set of hosts that our syscall implementation will work on, because if the direct syscall fails ENOSYS then the libc functions would also fail ENOSYS. (The system call has been in the kernel since 2.6.22 anyway.) Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
This commit is contained in:
parent
6080723102
commit
700fa58e4b
@ -520,16 +520,7 @@ static int sys_getcwd1(char *buf, size_t size)
|
||||
}
|
||||
|
||||
#ifdef TARGET_NR_utimensat
|
||||
#ifdef CONFIG_UTIMENSAT
|
||||
static int sys_utimensat(int dirfd, const char *pathname,
|
||||
const struct timespec times[2], int flags)
|
||||
{
|
||||
if (pathname == NULL)
|
||||
return futimens(dirfd, times);
|
||||
else
|
||||
return utimensat(dirfd, pathname, times, flags);
|
||||
}
|
||||
#elif defined(__NR_utimensat)
|
||||
#if defined(__NR_utimensat)
|
||||
#define __NR_sys_utimensat __NR_utimensat
|
||||
_syscall4(int,sys_utimensat,int,dirfd,const char *,pathname,
|
||||
const struct timespec *,tsp,int,flags)
|
||||
|
Loading…
Reference in New Issue
Block a user