Re: [syzbot] WARNING in kvm_wait
On Tue, Mar 9, 2021 at 12:29 AM 'Sean Christopherson' via syzkaller-bugs wrote: > > On Mon, Mar 08, 2021, syzbot wrote: > > Hello, > > > > syzbot found the following issue on: > > > > HEAD commit:a38fd874 Linux 5.12-rc2 > > git tree: upstream > > console output: https://syzkaller.appspot.com/x/log.txt?x=14158fdad0 > > kernel config: https://syzkaller.appspot.com/x/.config?x=db9c6adb4986f2f2 > > dashboard link: https://syzkaller.appspot.com/bug?extid=3c2bc6358072ede0f11b > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1096d35cd0 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf1e52d0 > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > Reported-by: syzbot+3c2bc6358072ede0f...@syzkaller.appspotmail.com > > Wanpeng has a patch posted to fix this[*], is there a way to retroactively > point > syzbot at that fix? > > [*] > https://lkml.kernel.org/r/1614057902-23774-1-git-send-email-wanpen...@tencent.com Great! Yes, it can be communicated to syzbot with: #syz fix: x86/kvm: Fix broken irq restoration in kvm_wait For details see: http://bit.do/syzbot#communication-with-syzbot
Re: [syzbot] WARNING in kvm_wait
On Mon, Mar 08, 2021, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:a38fd874 Linux 5.12-rc2 > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=14158fdad0 > kernel config: https://syzkaller.appspot.com/x/.config?x=db9c6adb4986f2f2 > dashboard link: https://syzkaller.appspot.com/bug?extid=3c2bc6358072ede0f11b > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1096d35cd0 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf1e52d0 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+3c2bc6358072ede0f...@syzkaller.appspotmail.com Wanpeng has a patch posted to fix this[*], is there a way to retroactively point syzbot at that fix? [*] https://lkml.kernel.org/r/1614057902-23774-1-git-send-email-wanpen...@tencent.com
[syzbot] WARNING in kvm_wait
Hello, syzbot found the following issue on: HEAD commit:a38fd874 Linux 5.12-rc2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14158fdad0 kernel config: https://syzkaller.appspot.com/x/.config?x=db9c6adb4986f2f2 dashboard link: https://syzkaller.appspot.com/bug?extid=3c2bc6358072ede0f11b syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1096d35cd0 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf1e52d0 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+3c2bc6358072ede0f...@syzkaller.appspotmail.com [ cut here ] raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 0 PID: 14236 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10 Modules linked in: CPU: 0 PID: 14236 Comm: syz-executor143 Not tainted 5.12.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10 Code: be ff cc cc cc cc cc cc cc cc cc cc cc 80 3d ac 2b b0 04 00 74 01 c3 48 c7 c7 a0 8f 6b 89 c6 05 9b 2b b0 04 01 e8 f7 cb be ff <0f> 0b c3 48 39 77 10 0f 84 97 00 00 00 66 f7 47 22 f0 ff 74 4b 48 RSP: 0018:c9000c29f9c0 EFLAGS: 00010286 RAX: RBX: c9e1b688 RCX: RDX: 88801e689bc0 RSI: 815c0eb5 RDI: f52001853f2a RBP: 0200 R08: R09: R10: 815b9c4e R11: R12: 0003 R13: f520001c36d1 R14: 0001 R15: 8880b9c35f40 FS: 018ce300() GS:8880b9c0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7ffd79af41d8 CR3: 1c373000 CR4: 00350ef0 Call Trace: kvm_wait arch/x86/kernel/kvm.c:860 [inline] kvm_wait+0xc9/0xe0 arch/x86/kernel/kvm.c:837 pv_wait arch/x86/include/asm/paravirt.h:564 [inline] pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:470 [inline] __pv_queued_spin_lock_slowpath+0x8b8/0xb40 kernel/locking/qspinlock.c:508 pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:554 [inline] queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline] queued_spin_lock include/asm-generic/qspinlock.h:85 [inline] do_raw_spin_lock+0x200/0x2b0 kernel/locking/spinlock_debug.c:113 spin_lock include/linux/spinlock.h:354 [inline] futex_wake+0x1b5/0x490 kernel/futex.c:1610 do_futex+0x326/0x1710 kernel/futex.c:3740 __do_sys_futex+0x2a2/0x470 kernel/futex.c:3798 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x4459c9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:7ffd79af41f8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: ffda RBX: RCX: 004459c9 RDX: 000f4240 RSI: 0081 RDI: 004ca408 RBP: 004ca400 R08: R09: R10: 7ffd79bec090 R11: 0246 R12: 7ffd79af4230 R13: 004ca40c R14: 0001 R15: 004023b0 --- 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 syzkal...@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
