Hi Arnd and Stepan,
> On Mon, Apr 22, 2019 at 11:07 AM Stepan Golosunov
> wrote:
> > 20.04.2019 в 13:21:12 +0200 Lukasz Majewski написал:
> > Is it? The kernel (5.1-rc6) code looks to me like
> >
> > /* Zero out the padding for 32 bit systems or in compat
> > mode */ if (false && false)
>
On Mon, Apr 22, 2019 at 11:07 AM Stepan Golosunov
wrote:
> 20.04.2019 в 13:21:12 +0200 Lukasz Majewski написал:
> Is it? The kernel (5.1-rc6) code looks to me like
>
> /* Zero out the padding for 32 bit systems or in compat mode */
> if (false && false)
> kts.tv_nse
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;
>
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;
> > + return INLINE_SYSCALL_CALL (clock_settime64, clock_id, &ts);
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
5 matches
Mail list logo