From 93a92d3bd649cd315db47b9fb5dcb6af657cc22c Mon Sep 17 00:00:00 2001 From: Riku Voipio Date: Mon, 15 Feb 2016 15:38:40 +0200 Subject: linux-user: correct timerfd_create syscall numbers x86, m68k, ppc, sh4 and sparc failed to enable timerfd, because they didn't have timerfd_create system call defined. Instead QEMU defined timerfd syscall. Checking with kernel sources, it appears kernel developers reused timerfd syscall number with timerfd_create, presumably since no userspace called the old syscall number. Reported-by: Laurent Vivier Reviewed-by: Laurent Vivier Signed-off-by: Riku Voipio --- linux-user/sh4/syscall_nr.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'linux-user/sh4/syscall_nr.h') diff --git a/linux-user/sh4/syscall_nr.h b/linux-user/sh4/syscall_nr.h index bdf8742c69..50099846d2 100644 --- a/linux-user/sh4/syscall_nr.h +++ b/linux-user/sh4/syscall_nr.h @@ -323,7 +323,7 @@ #define TARGET_NR_epoll_pwait 319 #define TARGET_NR_utimensat 320 #define TARGET_NR_signalfd 321 -#define TARGET_NR_timerfd 322 +#define TARGET_NR_timerfd_create 322 #define TARGET_NR_eventfd 323 #define TARGET_NR_fallocate 324 #define TARGET_NR_timerfd_settime 325 -- cgit v1.2.3