Re: [PATCH v2 2/7] y2038: Introduce __ASSUME_64BIT_TIME define

2019-05-05 Thread Stepan Golosunov
02.05.2019 в 15:04:18 + Joseph Myers написал: > On Tue, 30 Apr 2019, Lukasz Majewski wrote: > > > - The need for explicit clearing padding when calling syscalls (as to > >be better safe than sorry in the future - there was related > >discussion started by Stepan). > > This really isn

Re: [PATCH 1/2] y2038: make CONFIG_64BIT_TIME unconditional

2019-04-27 Thread Stepan Golosunov
27.04.2019 в 00:46:53 +0200 Lukasz Majewski написал: > Hi Arnd, > > > As Stepan Golosunov points out, we made a small mistake in the > > get_timespec64() function in the kernel. It was originally added under > > the assumption that CONFIG_64BIT_TIME would get enabled on a

Re: [PATCH 3/6] y2038: linux: Provide __clock_settime64 implementation

2019-04-22 Thread Stepan Golosunov
20.04.2019 в 13:21:12 +0200 Lukasz Majewski написал: > Hi Stepan, > > > 15.04.2019 в 00:08:38 +0200 Lukasz Majewski написал: > > > +# if defined __NR_clock_settime64 > > > + /* Make sure that passed __timespec64 struct pad is 0. */ > > > + struct __timespec64 ts = *tp; > > > + ts.tv_pad = 0; >

Re: [PATCH 3/6] y2038: linux: Provide __clock_settime64 implementation

2019-04-19 Thread Stepan Golosunov
15.04.2019 в 00:08:38 +0200 Lukasz Majewski написал: > +# if defined __NR_clock_settime64 > + /* Make sure that passed __timespec64 struct pad is 0. */ > + struct __timespec64 ts = *tp; > + ts.tv_pad = 0; > + return INLINE_SYSCALL_CALL (clock_settime64, clock_id, &ts); Isn't kernel supposed t