From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+904752567107eefb728c@syzkaller.appspotmail.com>
Cc: bp@alien8.de, eesposit@redhat.com, gregkh@linuxfoundation.org,
hpa@zytor.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com, rafael@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: kernel BUG at arch/x86/kvm/mmu/mmu.c:LINE! (2)
Date: Tue, 26 May 2020 17:12:13 -0700 [thread overview]
Message-ID: <20200527001213.GA31696@linux.intel.com> (raw)
In-Reply-To: <000000000000935ffd05a6939060@google.com>
On Tue, May 26, 2020 at 02:13:19PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: c11d28ab Add linux-next specific files for 20200522
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=153b5016100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3f6dbdea4159fb66
> dashboard link: https://syzkaller.appspot.com/bug?extid=904752567107eefb728c
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11510cba100000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=129301e2100000
>
> The bug was bisected to:
>
> commit 63d04348371b7ea4a134bcf47c79763d969e9168
> Author: Paolo Bonzini <pbonzini@redhat.com>
> Date: Tue Mar 31 22:42:22 2020 +0000
>
> KVM: x86: move kvm_create_vcpu_debugfs after last failure point
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1226e8ee100000
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1126e8ee100000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1626e8ee100000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+904752567107eefb728c@syzkaller.appspotmail.com
> Fixes: 63d04348371b ("KVM: x86: move kvm_create_vcpu_debugfs after last failure point")
>
> L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
> ------------[ cut here ]------------
> kernel BUG at arch/x86/kvm/mmu/mmu.c:3722!
The bisection has a completely different signature, it's likely a different
bug. I'll take a look at both.
prev parent reply other threads:[~2020-05-27 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 21:13 kernel BUG at arch/x86/kvm/mmu/mmu.c:LINE! (2) syzbot
2020-05-27 0:12 ` Sean Christopherson [this message]
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=20200527001213.GA31696@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=eesposit@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rafael@kernel.org \
--cc=syzbot+904752567107eefb728c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.