[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1911141601040.2507@nanos.tec.linutronix.de>
Date: Thu, 14 Nov 2019 16:02:09 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Dmitry Vyukov <dvyukov@...gle.com>
cc: syzbot <syzbot+dccce9b26ba09ca49966@...kaller.appspotmail.com>,
John Stultz <john.stultz@...aro.org>,
LKML <linux-kernel@...r.kernel.org>, sboyd@...nel.org,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
the arch/x86 maintainers <x86@...nel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Jann Horn <jannh@...gle.com>
Subject: Re: linux-next boot error: general protection fault in
__x64_sys_settimeofday
On Thu, 14 Nov 2019, Dmitry Vyukov wrote:
> On Thu, Nov 14, 2019 at 1:35 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> Looks like a plain user memory access:
>
> SYSCALL_DEFINE2(settimeofday, struct __kernel_old_timeval __user *, tv,
> struct timezone __user *, tz)
> {
> ....
> if (tv->tv_usec > USEC_PER_SEC) // <==== HERE
> return -EINVAL;
Bah, I looked at a stale next ....
Powered by blists - more mailing lists