From: syzbot <syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
jarkko@kernel.org, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sgx@vger.kernel.org, mingo@redhat.com, pbonzini@redhat.com,
seanjc@google.com, syzkaller-lts-bugs@googlegroups.com,
tglx@linutronix.de, usama.anjum@collabora.com,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [v5.15] WARNING in kvm_arch_vcpu_ioctl_run
Date: Sun, 26 Nov 2023 07:24:13 -0800 [thread overview]
Message-ID: <0000000000001bfd01060b0fc7dc@google.com> (raw)
In-Reply-To: <000000000000ad704b05f8de7e19@google.com>
This bug is marked as fixed by commit:
KVM: x86: Remove WARN sanity check on hypervisor timer vs. UNINITIALIZED vCPU
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Linux 5.15
Dashboard link: https://syzkaller.appspot.com/bug?extid=412c9ae97b4338c5187e
---
[1] I expect the commit to be present in:
1. linux-5.15.y branch of
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
next parent reply other threads:[~2023-11-26 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ad704b05f8de7e19@google.com>
2023-11-26 15:24 ` syzbot [this message]
2023-11-27 8:40 ` [v5.15] WARNING in kvm_arch_vcpu_ioctl_run Muhammad Usama Anjum
2023-12-11 8:41 ` syzbot
2023-12-25 8:42 ` syzbot
2024-01-09 18:18 ` syzbot
2024-01-10 5:09 ` Muhammad Usama Anjum
[not found] <00000000000099cf1805faee14d7@google.com>
2023-08-28 15:07 ` Muhammad Usama Anjum
2023-08-28 15:11 ` Sean Christopherson
2023-08-28 15:23 ` Muhammad Usama Anjum
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=0000000000001bfd01060b0fc7dc@google.com \
--to=syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzkaller-lts-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox