From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+7e2ab84953e4084a638d@syzkaller.appspotmail.com>
Cc: casey@schaufler-ca.com, frederic@kernel.org,
gregkh@linuxfoundation.org, hpa@zytor.com, jmattson@google.com,
jmorris@namei.org, karahmed@amazon.de,
kstewart@linuxfoundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, mingo@kernel.org,
mingo@redhat.com, pasha.tatashin@oracle.com, pbonzini@redhat.com,
pombredanne@nexb.com, rkrcmar@redhat.com, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: general protection fault in __schedule (2)
Date: Fri, 22 Nov 2019 12:54:53 -0800 [thread overview]
Message-ID: <20191122205453.GE31235@linux.intel.com> (raw)
In-Reply-To: <0000000000005eb1070597ea3a1f@google.com>
On Thu, Nov 21, 2019 at 11:19:00PM -0800, 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=124cdbace00000
> start commit: 234b69e3 ocfs2: fix ocfs2 read block panic
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=114cdbace00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=164cdbace00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8
> dashboard link: https://syzkaller.appspot.com/bug?extid=7e2ab84953e4084a638d
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150f0a4e400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f67111400000
>
> Reported-by: syzbot+7e2ab84953e4084a638d@syzkaller.appspotmail.com
> Fixes: 8fcc4b5923af ("kvm: nVMX: Introduce KVM_CAP_NESTED_STATE")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Is there a way to have syzbot stop processing/bisecting these things
after a reasonable amount of time? The original crash is from August of
last year...
Note, the original crash is actually due to KVM's put_kvm() fd race, but
whatever we want to blame, it's a duplicate.
#syz dup: general protection fault in kvm_lapic_hv_timer_in_use
next prev parent reply other threads:[~2019-11-22 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 13:39 general protection fault in __schedule (2) syzbot
2019-11-22 7:19 ` syzbot
2019-11-22 20:54 ` Sean Christopherson [this message]
2019-11-23 5:15 ` Dmitry Vyukov
2019-11-25 17:54 ` Sean Christopherson
2019-11-28 9:53 ` Dmitry Vyukov
2019-12-02 16:56 ` Sean Christopherson
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=20191122205453.GE31235@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=casey@schaufler-ca.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=jmorris@namei.org \
--cc=karahmed@amazon.de \
--cc=kstewart@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=pbonzini@redhat.com \
--cc=pombredanne@nexb.com \
--cc=rkrcmar@redhat.com \
--cc=serge@hallyn.com \
--cc=syzbot+7e2ab84953e4084a638d@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.