From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: syzbot <syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com>,
syzkaller-lts-bugs@googlegroups.com,
syzbot <syzbot+b000b7d21f93fc69de32@syzkaller.appspotmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.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>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
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 20:07:16 +0500 [thread overview]
Message-ID: <edeca3d3-bf4c-4c5d-8879-dca5173b6659@collabora.com> (raw)
In-Reply-To: <00000000000099cf1805faee14d7@google.com>
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
> Modules linked in:
> CPU: 1 PID: 3502 Comm: syz-executor306 Not tainted 5.15.110-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x1d63/0x1f80 arch/x86/kvm/x86.c:10310
> Code: df e8 71 ac b9 00 e9 e5 fa ff ff 89 d9 80 e1 07 38 c1 0f 8c 26 fb ff ff 48 89 df e8 57 ac b9 00 e9 19 fb ff ff e8 4d 52 70 00 <0f> 0b e9 e0 fb ff ff 89 d9 80 e1 07 38 c1 0f 8c 63 fb ff ff 48 89
> RSP: 0018:ffffc90002bcfc60 EFLAGS: 00010293
> RAX: ffffffff810f8c33 RBX: 0000000000000000 RCX: ffff888012bc1d00
> RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
> RBP: dffffc0000000000 R08: ffffffff8116a882 R09: fffffbfff1bc744e
> R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888012bc1d00
> R13: ffff888077580000 R14: ffff8880775800f0 R15: ffff88801e2a9000
> FS: 000055555696f300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007fafc4b53130 CR3: 000000007c8ce000 CR4: 00000000003526e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3863
> vfs_ioctl fs/ioctl.c:51 [inline]
> __do_sys_ioctl fs/ioctl.c:874 [inline]
> __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x61/0xcb
> RIP: 0033:0x7fafc4ae1ed9
> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffd3bb98a48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 000000000000cdf3 RCX: 00007fafc4ae1ed9
> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
> RBP: 0000000000000000 R08: 00007ffd3bb98be8 R09: 00007ffd3bb98be8
> R10: 00007ffd3bb98be8 R11: 0000000000000246 R12: 00007ffd3bb98a5c
> R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
> </TASK>
>
>
> ---
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
>
--
BR,
Muhammad Usama Anjum
next parent reply other threads:[~2023-08-28 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000099cf1805faee14d7@google.com>
2023-08-28 15:07 ` Muhammad Usama Anjum [this message]
2023-08-28 15:11 ` [v5.15] WARNING in kvm_arch_vcpu_ioctl_run Sean Christopherson
2023-08-28 15:23 ` Muhammad Usama Anjum
[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=edeca3d3-bf4c-4c5d-8879-dca5173b6659@collabora.com \
--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).