From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com>
Cc: dvyukov@google.com, hpa@zytor.com, jmattson@google.com,
karahmed@amazon.de, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, rkrcmar@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: WARNING in free_loaded_vmcs (2)
Date: Mon, 1 Apr 2019 12:16:50 -0700 [thread overview]
Message-ID: <20190401191650.GB24070@linux.intel.com> (raw)
In-Reply-To: <000000000000b0ddb205855cad54@google.com>
On Sat, Mar 30, 2019 at 09:53:01PM -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 8fcc4b5923af5de58b80b53a069453b135693304
> Author: Jim Mattson <jmattson@google.com>
> Date: Tue Jul 10 09:27:20 2018 +0000
>
> kvm: nVMX: Introduce KVM_CAP_NESTED_STATE
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17fba63f200000
> start commit: 60c1f892 Merge tag 'dma-mapping-4.19-2' of git://git.infra..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1407a63f200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1007a63f200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4c7e83258d6e0156
> dashboard link: https://syzkaller.appspot.com/bug?extid=01bc9e7a8a3f138b71cf
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a6513e400000
>
> Reported-by: syzbot+01bc9e7a8a3f138b71cf@syzkaller.appspotmail.com
> Fixes: 8fcc4b5923af ("kvm: nVMX: Introduce KVM_CAP_NESTED_STATE")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Blech, this is horribly stale. Fixed by commit 5bea5123cbf0 ("KVM: VMX:
check nested state and CR4.VMXE against SMM").
#syz fix: KVM: VMX: check nested state and CR4.VMXE against SMM
prev parent reply other threads:[~2019-04-01 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:46 WARNING in free_loaded_vmcs (2) syzbot
2018-08-14 17:16 ` Paolo Bonzini
2018-08-14 20:41 ` Dmitry Vyukov
2018-08-21 16:42 ` Paolo Bonzini
2018-09-04 2:41 ` syzbot
2019-03-31 4:53 ` syzbot
2019-04-01 19:16 ` 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=20190401191650.GB24070@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzbot+01bc9e7a8a3f138b71cf@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 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.