[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ce4b8316-1529-48d2-aadf-2ea25670edcf@collabora.com>
Date: Mon, 27 Nov 2023 13:40:13 +0500
From: Muhammad Usama Anjum <usama.anjum@...labora.com>
To: syzbot <syzbot+412c9ae97b4338c5187e@...kaller.appspotmail.com>,
bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
jarkko@...nel.org, jmattson@...gle.com, joro@...tes.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-sgx@...r.kernel.org, mingo@...hat.com, pbonzini@...hat.com,
seanjc@...gle.com, syzkaller-lts-bugs@...glegroups.com,
tglx@...utronix.de, vkuznets@...hat.com, wanpengli@...cent.com,
x86@...nel.org
Cc: Muhammad Usama Anjum <usama.anjum@...labora.com>
Subject: Re: [v5.15] WARNING in kvm_arch_vcpu_ioctl_run
On 11/26/23 8:24 PM, syzbot wrote:
> 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.
The commit is already in 6.7-rc3:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b0151caf73a656b75b550e361648430233455a0
> Is it a correct commit? Please update it by replying:
>
> #syz fix: exact-commit-title
The title is already correct.
>
> 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
--
BR,
Muhammad Usama Anjum
Powered by blists - more mailing lists