From: "Muhammad Usama Anjum" <usama.anjum@collabora.com>
To: "Sean Christopherson" <seanjc@google.com>
Cc: syzbot <syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com>,
syzkaller-lts-bugs@googlegroups.com,
syzbot <syzbot+b000b7d21f93fc69de32@syzkaller.appspotmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Wanpeng Li" <wanpengli@tencent.com>,
"Jim Mattson" <jmattson@google.com>,
"Joerg Roedel" <joro@8bytes.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
x86@kernel.org, linux-sgx@vger.kernel.org
Subject: Re: [v5.15] WARNING in kvm_arch_vcpu_ioctl_run
Date: Mon, 28 Aug 2023 16:23:26 +0100 [thread overview]
Message-ID: <6ba2-64ecbc00-5-39397d40@6469447> (raw)
In-Reply-To: <ZOy5L4WCiy1hsiu0@google.com>
On Monday, August 28, 2023 08:11 PM PKT, Sean Christopherson <seanjc@google.com> wrote:
> On Mon, Aug 28, 2023, Muhammad Usama Anjum wrote:
> > On 5/5/23 1:28 PM, syzbot wrote:
> > > syzbot has found a reproducer for the following issue on:
> > >
> > > HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
> > This same warning has also been found on 6.1.21.
> >
> > > git tree: linux-5.15.y
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=15f12318280000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=ba8d5c9d6c5289f
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=412c9ae97b4338c5187e
> > > compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e13c84280000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149d9470280000
> > I've tried all the C and syz reproducers. I've also tried syz-crash which
> > launched multiple instances of VMs and ran syz reproducer. But the issue
> > didn't get reproduced.
> >
> > I don't have kvm skills. Can someone have a look at the the warning
> > (probably by static analysis)?
> >
> > >
> > > Downloadable assets:
> > > disk image: https://storage.googleapis.com/syzbot-assets/fc04f54c047f/disk-8a7f2a5c.raw.xz
> > > vmlinux: https://storage.googleapis.com/syzbot-assets/6b4ba4cb1191/vmlinux-8a7f2a5c.xz
> > > kernel image: https://storage.googleapis.com/syzbot-assets/d927dc3f9670/bzImage-8a7f2a5c.xz
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com
> > >
> > > ------------[ cut here ]------------
> > > WARNING: CPU: 0 PID: 3502 at arch/x86/kvm/x86.c:10310 kvm_arch_vcpu_ioctl_run+0x1d63/0x1f80
>
> "Fixed" by https://lore.kernel.org/all/20230808232057.2498287-1-seanjc@google.com,
> in quotes because sadly the fix was to simply delete the sanity check :-(
Thank you so much Sean. Thank you so much Sean. Syzbot has been finding the issue in LTS kernels. I'm not sure if we should backport a patch which is just removing a false warning.
#syz fix: KVM: x86: Remove WARN sanity check on hypervisor timer vs. UNINITIALIZED vCPU
next prev parent reply other threads:[~2023-08-28 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000099cf1805faee14d7@google.com>
2023-08-28 15:07 ` [v5.15] WARNING in kvm_arch_vcpu_ioctl_run Muhammad Usama Anjum
2023-08-28 15:11 ` Sean Christopherson
2023-08-28 15:23 ` Muhammad Usama Anjum [this message]
[not found] <000000000000ad704b05f8de7e19@google.com>
2023-11-26 15:24 ` syzbot
2023-11-27 8:40 ` 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
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=6ba2-64ecbc00-5-39397d40@6469447 \
--to=usama.anjum@collabora.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=syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com \
--cc=syzbot+b000b7d21f93fc69de32@syzkaller.appspotmail.com \
--cc=syzkaller-lts-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).