linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-clk@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	lkft-triage@lists.linaro.org, LTP List <ltp@lists.linux.it>,
	chrubis <chrubis@suse.cz>, John Stultz <john.stultz@linaro.org>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: linux-next: Tree for Nov 14
Date: Thu, 14 Nov 2019 15:11:04 -0500 (EST)	[thread overview]
Message-ID: <247236994.12271471.1573762264445.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYtpOaYDoUEzQuYxmKJLFH2GDvK3ipWienn-zHDB+nOMbg@mail.gmail.com>



----- 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.


  reply	other threads:[~2019-11-14 20:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  8:31 linux-next: Tree for Nov 14 Stephen Rothwell
2019-11-14 18:38 ` Naresh Kamboju
2019-11-14 20:11   ` Jan Stancek [this message]
2019-11-14 21:19     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14  3:19 Stephen Rothwell
2022-11-14  7:49 Stephen Rothwell
2018-11-14  5:26 Stephen Rothwell
2017-11-14  6:20 Stephen Rothwell
2016-11-14  7:23 Stephen Rothwell
2014-11-14  8:27 Stephen Rothwell
2014-11-15 21:19 ` Guenter Roeck
2014-11-16  2:33   ` Jiang Liu
2014-11-16  3:22     ` Guenter Roeck
2014-11-16  4:20       ` Jiang Liu
2014-11-16  6:56         ` Guenter Roeck
2014-11-16  8:24           ` Jiang Liu
2014-11-16  8:37             ` Jiang Liu
2014-11-16 15:42               ` Guenter Roeck
2014-11-16 16:01             ` Guenter Roeck
2014-11-16 16:11               ` Guenter Roeck
2014-11-17  5:12       ` Jiang Liu
2014-11-17 17:02         ` Guenter Roeck
2013-11-14  4:22 Stephen Rothwell
2012-11-14  5:30 Stephen Rothwell
2012-11-14  5:37 ` Andrew Morton
2012-11-14  5:53   ` Andrew Morton
2012-11-14  6:47   ` Ingo Molnar
2012-11-14  6:56     ` Andrew Morton
2012-11-14  7:15       ` Stephen Rothwell
2012-11-14  7:24         ` Andrew Morton
2012-11-14  7:39       ` Ingo Molnar
2012-11-14  8:13         ` Hugh Dickins
2012-11-14 17:05           ` Rik van Riel
2012-11-15 12:10             ` Mel Gorman
2012-11-14 17:19       ` Linus Torvalds
2012-11-14  6:55   ` Stephen Rothwell
2012-11-14  7:03     ` Stephen Rothwell
2011-11-14  3:43 Stephen Rothwell
2019-11-14 16:43 ` Christian Brauner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=247236994.12271471.1573762264445.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=chrubis@suse.cz \
    --cc=daniel.lezcano@linaro.org \
    --cc=dvyukov@google.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).