From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Christopherson Subject: Re: general protection fault in kvm_lapic_hv_timer_in_use Date: Mon, 1 Apr 2019 12:58:59 -0700 Message-ID: <20190401195859.GA25411@linux.intel.com> References: <0000000000006af1a90573251240@google.com> <0000000000009f67a70585603de2@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dvhart@infradead.org, hpa@zytor.com, jmattson@google.com, karahmed@amazon.de, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, pbonzini@redhat.com, peterz@infradead.org, rkrcmar@redhat.com, syzkaller-bugs@googlegroups.com, tglx@linutronix.de, x86@kernel.org To: syzbot Return-path: Content-Disposition: inline In-Reply-To: <0000000000009f67a70585603de2@google.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, Mar 31, 2019 at 02:08:00AM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 8fcc4b5923af5de58b80b53a069453b135693304 > Author: Jim Mattson > 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=127b4f43200000 > start commit: 234b69e3 ocfs2: fix ocfs2 read block panic > git tree: upstream > final crash: https://syzkaller.appspot.com/x/report.txt?x=117b4f43200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=167b4f43200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8 > dashboard link: https://syzkaller.appspot.com/bug?extid=1c69d94fe42901b029c1 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e14956400000 > > Reported-by: syzbot+1c69d94fe42901b029c1@syzkaller.appspotmail.com > Fixes: 8fcc4b5923af ("kvm: nVMX: Introduce KVM_CAP_NESTED_STATE") > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection Another ancient bug, fixed by commit 26b471c7e2f7 ("KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs") #syz fix: KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs