On Sat, Mar 6, 2021 at 12:28 PM syzbot <syzbot+46fc491326a456ff8...@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: edbea922 veth: Store queue_mapping independently of XDP pr.. > git tree: bpf > console output: https://syzkaller.appspot.com/x/log.txt?x=113ae02ad00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=402784bff477e1ac > dashboard link: https://syzkaller.appspot.com/bug?extid=46fc491326a456ff8127 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+46fc491326a456ff8...@syzkaller.appspotmail.com
#syz dup: upstream boot error: WARNING in kvm_wait > ------------[ cut here ]------------ > raw_local_irq_restore() called with IRQs enabled > WARNING: CPU: 0 PID: 4787 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: 4787 Comm: systemd-getty-g Not tainted 5.11.0-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 1e 62 b0 04 00 74 01 c3 48 > c7 c7 a0 8e 6b 89 c6 05 0d 62 b0 04 01 e8 57 da 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:ffffc900012efc40 EFLAGS: 00010282 > RAX: 0000000000000000 RBX: ffffffff8be28b80 RCX: 0000000000000000 > RDX: ffff888023de5340 RSI: ffffffff815bea35 RDI: fffff5200025df7a > RBP: 0000000000000200 R08: 0000000000000000 R09: 0000000000000001 > R10: ffffffff815b77be R11: 0000000000000000 R12: 0000000000000003 > R13: fffffbfff17c5170 R14: 0000000000000001 R15: ffff8880b9c35f40 > FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007fa257bcaab4 CR3: 000000000bc8e000 CR4: 00000000001506f0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > 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] > check_stack_usage kernel/exit.c:715 [inline] > do_exit+0x1d6a/0x2ae0 kernel/exit.c:868 > do_group_exit+0x125/0x310 kernel/exit.c:922 > __do_sys_exit_group kernel/exit.c:933 [inline] > __se_sys_exit_group kernel/exit.c:931 [inline] > __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:931 > do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 > entry_SYSCALL_64_after_hwframe+0x44/0xae > RIP: 0033:0x7fa2592a3618 > Code: Unable to access opcode bytes at RIP 0x7fa2592a35ee. > RSP: 002b:00007ffc579980b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 > RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa2592a3618 > RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 > RBP: 00007fa2595808e0 R08: 00000000000000e7 R09: fffffffffffffee8 > R10: 00007fa25775e158 R11: 0000000000000246 R12: 00007fa2595808e0 > R13: 00007fa259585c20 R14: 0000000000000000 R15: 0000000000000000 > > > --- > 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. > > -- > You received this message because you are subscribed to the Google Groups > "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to syzkaller-bugs+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/syzkaller-bugs/0000000000004094ff05bcdc7ffb%40google.com.
