From: syzbot <syzbot+f1d2136db9c80d4733e8@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, fgheet255t@gmail.com,
hpa@zytor.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, mlevitsk@redhat.com, pbonzini@redhat.com,
seanjc@google.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
x86@kernel.org
Subject: Re: [syzbot] WARNING in nested_vmx_vmexit
Date: Tue, 07 Dec 2021 11:19:14 -0800 [thread overview]
Message-ID: <000000000000af941b05d2933f28@google.com> (raw)
In-Reply-To: <00000000000051f90e05d2664f1d@google.com>
syzbot has bisected this issue to:
commit c8607e4a086fae05efe5bffb47c5199c65e7216e
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date: Mon Sep 13 14:09:53 2021 +0000
KVM: x86: nVMX: don't fail nested VM entry on invalid guest state if !from_vmentry
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f21e3ab00000
start commit: f80ef9e49fdf Merge tag 'docs-5.16-3' of git://git.lwn.net/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12f21e3ab00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14f21e3ab00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d5e878e3399b6cc
dashboard link: https://syzkaller.appspot.com/bug?extid=f1d2136db9c80d4733e8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1603533ab00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175b5f3db00000
Reported-by: syzbot+f1d2136db9c80d4733e8@syzkaller.appspotmail.com
Fixes: c8607e4a086f ("KVM: x86: nVMX: don't fail nested VM entry on invalid guest state if !from_vmentry")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-12-07 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 13:42 [syzbot] WARNING in nested_vmx_vmexit syzbot
2021-12-06 9:16 ` Vitaly Kuznetsov
2021-12-06 16:05 ` Sean Christopherson
2021-12-06 16:16 ` Vitaly Kuznetsov
2021-12-06 16:45 ` Sean Christopherson
2021-12-06 17:21 ` Sean Christopherson
2021-12-06 17:22 ` Sean Christopherson
2021-12-07 8:20 ` Maxim Levitsky
2021-12-07 11:20 ` syzbot
2021-12-07 19:19 ` syzbot [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=000000000000af941b05d2933f28@google.com \
--to=syzbot+f1d2136db9c80d4733e8@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fgheet255t@gmail.com \
--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=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox