Re: linux-next: Tree for Nov 14

[Arnd Bergmann <arnd@arndb.de>]

On Thu, Nov 14, 2019 at 9:11 PM Jan Stancek <jstancek@redhat.com> wrote:
>
>
>
> ----- Original Message -----
> > On Thu, 14 Nov 2019 at 14:01, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Hi all,
> > > Changes since 20191113:
> > > The y2038 tree gained a build failure for which I applied a patch.
> > <trim>
> > > The akpm-current tree gained a conflict against the y2038 tree.
> > >
> > > Non-merge commits (relative to Linus' tree): 10388
> > >  9238 files changed, 397357 insertions(+), 174171 deletions(-)
> >
> > Results from Linaro’s test farm.
> > Regressions detected on x86_64, and i386.
> >
> > LTP syscalls settimeofday01/02 failed on x86_64 and i386 running
> > 5.4.0-rc7-next-20191114.
> >
> > Following  ltp-syscalls-tests failed.
> >     * settimeofday01
> >     * settimeofday02
> >     * stime01
> >     * stime02
>
> Looks like typo in
> adde74306a4b ("y2038: time: avoid timespec usage in settimeofday()")
>
> -               if (!timeval_valid(&user_tv))
> +               if (tv->tv_usec > USEC_PER_SEC)
>
> was likely meant as:
>
> -               if (!timeval_valid(&user_tv))
> +               if (new_ts.tv_nsec > USEC_PER_SEC)
>
> since tv is user pointer.
>

I have uploaded a fixed version, sorry for the breakage. The new version also
addresses the build failure that Stephen reported.

        Arnd