All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b1784a9a955885da51cd@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-x86?] WARNING in kvm_apic_accept_events
Date: Sat, 11 Oct 2025 19:53:02 -0700	[thread overview]
Message-ID: <68eb180e.a70a0220.b3ac9.0010.GAE@google.com> (raw)
In-Reply-To: <684196cd.050a0220.2461cf.001e.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 0fe3e8d804fdcc09ef44fbffcad8c39261a03470
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jun 5 19:50:17 2025 +0000

    KVM: x86: Move INIT_RECEIVED vs. INIT/SIPI blocked check to KVM_RUN

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1585c9e2580000
start commit:   64980441d269 Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=26abb92f9ef9d1d0
dashboard link: https://syzkaller.appspot.com/bug?extid=b1784a9a955885da51cd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12200c0c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16fd31d4580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: KVM: x86: Move INIT_RECEIVED vs. INIT/SIPI blocked check to KVM_RUN

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2025-10-12  2:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 13:08 [syzbot] [kvm-x86?] WARNING in kvm_apic_accept_events syzbot
2025-06-05 13:15 ` Sean Christopherson
2025-10-12  2:53 ` syzbot [this message]
2025-10-13 13:37   ` 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=68eb180e.a70a0220.b3ac9.0010.GAE@google.com \
    --to=syzbot+b1784a9a955885da51cd@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 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.