lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20190121121923.GF4020@osiris> Date: Mon, 21 Jan 2019 13:19:24 +0100 From: Heiko Carstens <heiko.carstens@...ibm.com> To: Arnd Bergmann <arnd@...db.de> Cc: y2038@...ts.linaro.org, linux-api@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, mattst88@...il.com, linux@...linux.org.uk, catalin.marinas@....com, will.deacon@....com, tony.luck@...el.com, fenghua.yu@...el.com, geert@...ux-m68k.org, monstr@...str.eu, paul.burton@...s.com, deller@....de, benh@...nel.crashing.org, mpe@...erman.id.au, schwidefsky@...ibm.com, dalias@...c.org, davem@...emloft.net, luto@...nel.org, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, x86@...nel.org, jcmvbkbc@...il.com, akpm@...ux-foundation.org, deepa.kernel@...il.com, ebiederm@...ssion.com, firoz.khan@...aro.org, linux-alpha@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-ia64@...r.kernel.org, linux-m68k@...ts.linux-m68k.org, linux-mips@...r.kernel.org, linux-parisc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org, linux-sh@...r.kernel.org, sparclinux@...r.kernel.org, netdev@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures 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@...db.de> > --- > arch/s390/kernel/syscalls/syscall.tbl | 20 +++++++++ For the s390 bits: Acked-by: Heiko Carstens <heiko.carstens@...ibm.com>
Powered by blists - more mailing lists