Thread (64 messages) 64 messages, 9 authors, 2019-01-25

Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures

From: Heiko Carstens <hidden>
Date: 2019-01-21 12:19:42
Also in: linux-api, linux-arch, linux-arm-kernel, linux-fsdevel, linux-mips, linux-sh, linuxppc-dev, lkml, netdev, sparclinux

On Fri, Jan 18, 2019 at 05:18:35PM +0100, Arnd Bergmann wrote:
This adds 21 new system calls on each ABI that has 32-bit time_t
today. All of these have the exact same semantics as their existing
counterparts, and the new ones all have macro names that end in 'time64'
for clarification.

This gets us to the point of being able to safely use a C library
that has 64-bit time_t in user space. There are still a couple of
loose ends to tie up in various areas of the code, but this is the
big one, and should be entirely uncontroversial at this point.

In particular, there are four system calls (getitimer, setitimer,
waitid, and getrusage) that don't have a 64-bit counterpart yet,
but these can all be safely implemented in the C library by wrapping
around the existing system calls because the 32-bit time_t they
pass only counts elapsed time, not time since the epoch. They
will be dealt with later.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
 arch/s390/kernel/syscalls/syscall.tbl       | 20 +++++++++
For the s390 bits:
Acked-by: Heiko Carstens <redacted>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help