All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9dcd0a11dc9703a49511@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com,  pbonzini@redhat.com, seanjc@google.com,
	syzkaller-bugs@googlegroups.com,  tglx@kernel.org,
	x86@kernel.org
Subject: [syzbot] [kvm-x86?] WARNING in kvm_check_and_inject_events
Date: Thu, 09 Jul 2026 09:33:28 -0700	[thread overview]
Message-ID: <6a4fcd58.a1ad617e.25832.000f.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    0e35b9b6ec0f Merge tag 'mm-hotfixes-stable-2026-07-06-17-4..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1144b739580000
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
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=129d4389580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10de8432580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-0e35b9b6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c14bac7bee17/vmlinux-0e35b9b6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/36bfa5293255/bzImage-0e35b9b6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9dcd0a11dc9703a49511@syzkaller.appspotmail.com

------------[ 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#0: syz.2.478/7431
Modules linked in:
CPU: 0 UID: 0 PID: 7431 Comm: syz.2.478 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 51 44 7e 00 90 0f 0b 90 e9 b7 fe ff ff e8 43 44 7e 00 90 <0f> 0b 90 e9 2e f8 ff ff e8 d5 bd ee 00 e9 ae f6 ff ff 48 8b 7c 24
RSP: 0018:ffffc90003e77a20 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8880564729c0 RCX: ffffffff818b8adc
RDX: ffff888027f40000 RSI: ffffffff818b8bfd RDI: ffff888027f40000
RBP: 00000000ffffffff R08: 0000000000000005 R09: 00000000ffffffff
R10: 00000000ffffffff R11: 0000000000000000 R12: ffff8880564735ec
R13: 0000000000000001 R14: ffff888056472ca8 R15: ffff8880564732f8
FS:  000055558b257500(0000) GS:ffff8880d5dec000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb475a73780 CR3: 0000000034df7000 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:0x7fb475b9de59
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:00007ffc07cddbe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fb475e25fa0 RCX: 00007fb475b9de59
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00007fb475c33e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb475e25fac R14: 00007fb475e25fa0 R15: 00007fb475e25fa0
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2026-07-09 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 16:33 syzbot [this message]
2026-07-12  2:09 ` Forwarded: [PATCH] KVM: x86: Add debug traces to investigate irq == -1 syzbot
2026-07-12  4:36 ` Forwarded: [PATCH] KVM: x86: Add debug traces (KERN_WARNING) to investigate irq syzbot
     [not found] <20260712020904.29847-1-kartikey406@gmail.com>
2026-07-12  2:32 ` [syzbot] [kvm-x86?] WARNING in kvm_check_and_inject_events syzbot
     [not found] <20260712043621.31248-1-kartikey406@gmail.com>
2026-07-12  4:57 ` 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=6a4fcd58.a1ad617e.25832.000f.GAE@google.com \
    --to=syzbot+9dcd0a11dc9703a49511@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@kernel.org \
    --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 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.