[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALCETrXreVrWEsBBYX8KS=-DFW=5RB7SAKcgcdPtzJtML6n7UQ@mail.gmail.com>
Date: Sun, 19 Jul 2020 08:12:45 -0700
From: Andy Lutomirski <luto@...nel.org>
To: syzbot <syzbot+29454675f5fe94137999@...kaller.appspotmail.com>
Cc: Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
syzkaller-bugs@...glegroups.com,
Thomas Gleixner <tglx@...utronix.de>, X86 ML <x86@...nel.org>
Subject: Re: WARNING in do_syscall_64
On Sun, Jul 19, 2020 at 12:42 AM syzbot
<syzbot+29454675f5fe94137999@...kaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e9919e11 Merge branch 'for-linus' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11dca4cf100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e944500a36bc4d55
> dashboard link: https://syzkaller.appspot.com/bug?extid=29454675f5fe94137999
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
>
> Unfortunately, I don't have any reproducer for this issue yet.
On a brief inspection, the only way I can see this happening is if the
syscall flags msr got corrupted. There's not much code between the
actual hardware entry and this warning.
--Andy
Powered by blists - more mailing lists