aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2018-04-18 16:18:35 +0200
committerArnd Bergmann <arnd@arndb.de>2018-12-18 16:13:04 +0100
commit2367c4b5fa09b2947d03c5cd23d7bc0200b7fe4f (patch)
treefcced38c7b41fa8a17cae5a05f4cdd17f2eb907c /arch
parenty2038: signal: Add sys_rt_sigtimedwait_time32 (diff)
downloadlinux-dev-2367c4b5fa09b2947d03c5cd23d7bc0200b7fe4f.tar.xz
linux-dev-2367c4b5fa09b2947d03c5cd23d7bc0200b7fe4f.zip
y2038: signal: Add compat_sys_rt_sigtimedwait_time64
Now that 32-bit architectures have two variants of sys_rt_sigtimedwaid() for 32-bit and 64-bit time_t, we also need to have a second compat system call entry point on the corresponding 64-bit architectures. The traditional system call keeps getting handled by compat_sys_rt_sigtimedwait(), and this adds a new compat_sys_rt_sigtimedwait_time64() that differs only in the timeout argument type. The naming remains a bit asymmetric for the moment. Ideally we would want to have compat_sys_rt_sigtimedwait_time32() for the old version and compat_sys_rt_sigtimedwait() for the new one to mirror the names of the native entry points, but renaming the existing system call tables causes unnecessary churn. I would suggest renaming all such system calls together at a later point. Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions