From: Arnd Bergmann <arnd@arndb.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
syzbot <syzbot+dccce9b26ba09ca49966@syzkaller.appspotmail.com>,
John Stultz <john.stultz@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Jann Horn <jannh@google.com>
Subject: Re: linux-next boot error: general protection fault in __x64_sys_settimeofday
Date: Thu, 14 Nov 2019 14:22:06 +0100 [thread overview]
Message-ID: <CAK8P3a1ybsTEgBd_oOeReTppO=mDBu+6rGufA8Lf+UGK+SgA-A@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+ap9wFaOq-3WhO3-QnW7dCFWArvozQHKxBcmzR3wppvFQ@mail.gmail.com>
On Thu, Nov 14, 2019 at 1:43 PM Dmitry Vyukov <dvyukov@google.com> wrote:
>
> On Thu, Nov 14, 2019 at 1:42 PM Dmitry Vyukov <dvyukov@google.com> wrote:
> >
> > On Thu, Nov 14, 2019 at 1:35 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> > >
> > > On Thu, 14 Nov 2019, syzbot wrote:
> > >
> > > From the full console output:
> >
> > Urgently need +Jann's patch to better explain these things!
>
> +Arnd, this does not look right:
>
> commit adde74306a4b05c04dc51f31a08240faf6e97aa9
> Author: Arnd Bergmann <arnd@arndb.de>
> Date: Wed Aug 15 20:04:11 2018 +0200
>
> y2038: time: avoid timespec usage in settimeofday()
> ...
>
> - if (!timeval_valid(&user_tv))
> + if (tv->tv_usec > USEC_PER_SEC)
> return -EINVAL;
Thanks for the report!
I was checking the wrong variable, fixed now,
should push it out to my y2038 branch in a bit.
Arnd
next prev parent reply other threads:[~2019-11-14 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 10:55 linux-next boot error: general protection fault in __x64_sys_settimeofday syzbot
2019-11-14 12:35 ` Thomas Gleixner
2019-11-14 12:42 ` Dmitry Vyukov
2019-11-14 12:43 ` Dmitry Vyukov
2019-11-14 13:22 ` Arnd Bergmann [this message]
2019-11-14 13:28 ` Dmitry Vyukov
2019-11-14 13:37 ` Arnd Bergmann
2019-11-14 13:39 ` Dmitry Vyukov
2019-11-14 13:51 ` Arnd Bergmann
2019-11-14 15:02 ` Thomas Gleixner
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='CAK8P3a1ybsTEgBd_oOeReTppO=mDBu+6rGufA8Lf+UGK+SgA-A@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=jannh@google.com \
--cc=john.stultz@linaro.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=syzbot+dccce9b26ba09ca49966@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).