From: Arnd Bergmann <arnd@arndb.de>
To: y2038@lists.linaro.org
Cc: linux-kernel@vger.kernel.org,
Deepa Dinamani <deepa.kernel@gmail.com>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-api@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 0/5] y2038: further system call conversion
Date: Fri, 7 Dec 2018 22:18:03 +0100 [thread overview]
Message-ID: <20181207211808.328719-1-arnd@arndb.de> (raw)
This is another set of system call changes that were intended to get
merged much earlier. I've rebased the patches on top of the latest kernel
and Deepa's poll/select/io_pgetevents series now, and applied it to the
same y2038 branch for inclusion in 4.21.
This is just a continuation of the earlier system call changes, so I
expect no surprises here, unless I made a mistake in the rebase.
After this series, the only remaining system calls that need to be
modified are:
- setsockopt/getsockopt, they do not need a new entry in the system
call table, only new numbers assigned for their socket options.
Deepa is finalizing her series to passing 64-bit timestamps in cmsg
correctly for SO_TIMESTAMP{,NS,ING}.
Further, we need a new SO_RCVTIMEO/SO_SNDTIMEO implementation
here, which has not been implemented yet.
- waitid/getrusage, this needs a rewrite now from earlier versions
based on recent feedback. The plan now is to incorporate nanosecond
timestamps in a new revision of the 'rusage' structure. Possibly also
include BSD wait6() semantics of passing back the child resource
usage in waitid(), and/or a method to pass a signal mask as in
io_pgetevents(). waitid/getrusage() are not required for correct
behavior with 64-bit time_t and can be safely emulated on top of
the existing syscalls by the C library beyond 2038. This needs more
discussion.
- clock_adjtime, this is also optional and can be implemented
by the C library if necessary. The plan is to do the same as x32
and use the 64-bit structure natively on both 32-bit and 64-bit
architectures. The timex structure contains a 'timeval' at the
moment, but also supports nanoseconds passed in it.
- getitimer/setitimer, these again can be trivially emulated
by the C library.
Arnd
Arnd Bergmann (5):
y2038: futex: Move compat implementation into futex.c
y2038: futex: Add support for __kernel_timespec
y2038: socket: Add compat_sys_recvmmsg_time64
y2038: signal: Add sys_rt_sigtimedwait_time32
y2038: signal: Add compat_sys_rt_sigtimedwait_time64
include/linux/compat.h | 8 +-
include/linux/futex.h | 8 --
include/linux/socket.h | 9 +-
include/linux/syscalls.h | 9 +-
kernel/Makefile | 3 -
kernel/futex.c | 207 +++++++++++++++++++++++++++++++++++++--
kernel/futex_compat.c | 202 --------------------------------------
kernel/signal.c | 65 ++++++++++++
kernel/sys_ni.c | 2 +
net/compat.c | 34 +++----
net/socket.c | 62 +++++++++---
11 files changed, 345 insertions(+), 264 deletions(-)
delete mode 100644 kernel/futex_compat.c
--
2.18.0
next reply other threads:[~2018-12-07 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 21:18 Arnd Bergmann [this message]
2018-12-07 21:18 ` [PATCH 1/5] y2038: futex: Move compat implementation into futex.c Arnd Bergmann
2018-12-07 21:18 ` [PATCH 2/5] y2038: futex: Add support for __kernel_timespec Arnd Bergmann
2018-12-07 21:18 ` [PATCH 3/5] y2038: socket: Add compat_sys_recvmmsg_time64 Arnd Bergmann
2018-12-07 21:18 ` [PATCH 4/5] y2038: signal: Add sys_rt_sigtimedwait_time32 Arnd Bergmann
2018-12-07 21:18 ` [PATCH 5/5] y2038: signal: Add compat_sys_rt_sigtimedwait_time64 Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181207211808.328719-1-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).