From: syzbot <syzbot+1522459a74d26b0ac33a@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [kvm?] WARNING in vcpu_run
Date: Tue, 10 Dec 2024 01:38:04 -0800 [thread overview]
Message-ID: <67580bfc.050a0220.a30f1.01c7.GAE@google.com> (raw)
In-Reply-To: <671bc7a7.050a0220.455e8.022a.GAE@google.com>
syzbot has bisected this issue to:
commit 45405155d876c326da89162b8173b8cc9ab7ed75
Author: Sean Christopherson <seanjc@google.com>
Date: Fri Jun 7 17:26:09 2024 +0000
KVM: x86: WARN if a vCPU gets a valid wakeup that KVM can't yet inject
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11ac34df980000
start commit: ae90f6a6170d Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13ac34df980000
console output: https://syzkaller.appspot.com/x/log.txt?x=15ac34df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28
dashboard link: https://syzkaller.appspot.com/bug?extid=1522459a74d26b0ac33a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=158d0230580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f8de40580000
Reported-by: syzbot+1522459a74d26b0ac33a@syzkaller.appspotmail.com
Fixes: 45405155d876 ("KVM: x86: WARN if a vCPU gets a valid wakeup that KVM can't yet inject")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-10 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 16:30 [syzbot] [kvm?] WARNING in vcpu_run syzbot
2024-12-10 9:38 ` syzbot [this message]
2026-01-03 20:51 ` Forwarded: " syzbot
2026-01-03 21:46 ` syzbot
[not found] <CAKiXHKc_LQaT5-i+CJKt_xvLf5uQ6_0DkPSjJKdrqK9CH6ZnVA@mail.gmail.com>
2026-01-03 21:22 ` syzbot
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=67580bfc.050a0220.a30f1.01c7.GAE@google.com \
--to=syzbot+1522459a74d26b0ac33a@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox