From: syzbot <syzbot+9dcd0a11dc9703a49511@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kvm-x86?] WARNING in kvm_check_and_inject_events
Date: Sat, 11 Jul 2026 19:32:02 -0700 [thread overview]
Message-ID: <6a52fca2.574492cf.19a3b.000c.GAE@google.com> (raw)
In-Reply-To: <20260712020904.29847-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in kvm_check_and_inject_events
------------[ cut here ]------------
irq == -1
WARNING: arch/x86/kvm/x86.c:10800 at kvm_check_and_inject_events+0xf1e/0x1070 arch/x86/kvm/x86.c:10800, CPU#3: syz.0.69/6653
Modules linked in:
CPU: 3 UID: 0 PID: 6653 Comm: syz.0.69 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:kvm_check_and_inject_events+0xf1e/0x1070 arch/x86/kvm/x86.c:10800
Code: 00 48 8b 44 24 20 48 0d 00 01 01 00 48 89 44 24 10 e9 35 fd ff ff e8 a1 4e 7e 00 90 0f 0b 90 e9 b7 fe ff ff e8 93 4e 7e 00 90 <0f> 0b 90 e9 2e f8 ff ff e8 45 c8 ee 00 e9 ae f6 ff ff 48 8b 7c 24
RSP: 0018:ffffc90004137a20 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88803a0fa9c0 RCX: ffffffff818b8bac
RDX: ffff8880565a8000 RSI: ffffffff818b8ccd RDI: ffff8880565a8000
RBP: 00000000ffffffff R08: 0000000000000005 R09: 00000000ffffffff
R10: 00000000ffffffff R11: 0000000000000000 R12: ffff88803a0fb5ec
R13: 0000000000000001 R14: ffff88803a0faca8 R15: ffff88803a0fb2f8
FS: 00007f76f1fb46c0(0000) GS:ffff8880d60e8000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f76f1073780 CR3: 000000003e0e3000 CR4: 0000000000352ef0
Call Trace:
<TASK>
vcpu_enter_guest arch/x86/kvm/x86.c:11296 [inline]
vcpu_run+0xf1d/0x5d50 arch/x86/kvm/x86.c:11707
kvm_arch_vcpu_ioctl_run+0x5b6/0x1890 arch/x86/kvm/x86.c:12062
kvm_vcpu_ioctl+0x730/0x1700 virt/kvm/kvm_main.c:4470
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f76f119de59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f76f1fb4028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f76f1425fa0 RCX: 00007f76f119de59
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00007f76f1233e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f76f1426038 R14: 00007f76f1425fa0 R15: 00007fff9f7ea3a8
</TASK>
Tested on:
commit: 44696aa3 Merge tag 'input-for-v7.2-rc2' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17611b89580000
kernel config: https://syzkaller.appspot.com/x/.config?x=48ef5c5c0f192153
dashboard link: https://syzkaller.appspot.com/bug?extid=9dcd0a11dc9703a49511
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=1660f0b9580000
next parent reply other threads:[~2026-07-12 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260712020904.29847-1-kartikey406@gmail.com>
2026-07-12 2:32 ` syzbot [this message]
[not found] <20260712043621.31248-1-kartikey406@gmail.com>
2026-07-12 4:57 ` [syzbot] [kvm-x86?] WARNING in kvm_check_and_inject_events syzbot
2026-07-09 16:33 syzbot
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=6a52fca2.574492cf.19a3b.000c.GAE@google.com \
--to=syzbot+9dcd0a11dc9703a49511@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.