From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+7590ddacf9f333c18f6c@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, bp@alien8.de, hpa@zytor.com, jack@suse.cz,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
paolo.valente@linaro.org, pbonzini@redhat.com, reijiw@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] general protection fault in rcu_segcblist_enqueue
Date: Wed, 6 Oct 2021 22:52:05 +0000 [thread overview]
Message-ID: <YV4olbHUKr7edo9L@google.com> (raw)
In-Reply-To: <0000000000002f208405cdb6f447@google.com>
On Wed, Oct 06, 2021, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 067a456d091d05fdae32cae350410d905968b645
> Author: Sean Christopherson <seanjc@google.com>
> Date: Tue Jul 13 16:32:43 2021 +0000
>
> KVM: SVM: Require exact CPUID.0x1 match when stuffing EDX at INIT
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d871b7300000
> start commit: 0319b848b155 binfmt: a.out: Fix bogus semicolon
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=faed7df0f442c217
> dashboard link: https://syzkaller.appspot.com/bug?extid=7590ddacf9f333c18f6c
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1308d0ed300000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: KVM: SVM: Require exact CPUID.0x1 match when stuffing EDX at INIT
LOL, close? At least syzbot found a KVM commit.
#syz fix: KVM: x86: Handle SRCU initialization failure during page track init
prev parent reply other threads:[~2021-10-06 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 11:37 [syzbot] general protection fault in rcu_segcblist_enqueue syzbot
2021-08-14 8:05 ` syzbot
2021-10-06 22:49 ` syzbot
2021-10-06 22:52 ` 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=YV4olbHUKr7edo9L@google.com \
--to=seanjc@google.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paolo.valente@linaro.org \
--cc=pbonzini@redhat.com \
--cc=reijiw@google.com \
--cc=syzbot+7590ddacf9f333c18f6c@syzkaller.appspotmail.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 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.