All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+1c69d94fe42901b029c1@syzkaller.appspotmail.com>
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
Subject: Re: general protection fault in kvm_lapic_hv_timer_in_use
Date: Mon, 1 Apr 2019 12:58:59 -0700	[thread overview]
Message-ID: <20190401195859.GA25411@linux.intel.com> (raw)
In-Reply-To: <0000000000009f67a70585603de2@google.com>

On Sun, Mar 31, 2019 at 02:08:00AM -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=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

      reply	other threads:[~2019-04-01 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11  8:59 general protection fault in kvm_lapic_hv_timer_in_use syzbot
2018-09-21 14:44 ` syzbot
2019-03-31  9:08 ` syzbot
2019-04-01 19:58   ` 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=20190401195859.GA25411@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=dvhart@infradead.org \
    --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=peterz@infradead.org \
    --cc=rkrcmar@redhat.com \
    --cc=syzbot+1c69d94fe42901b029c1@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.