From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0CC7DC433DB for ; Fri, 5 Mar 2021 20:58:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 98FD264EDB for ; Fri, 5 Mar 2021 20:58:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229775AbhCEU5l (ORCPT ); Fri, 5 Mar 2021 15:57:41 -0500 Received: from mail-io1-f72.google.com ([209.85.166.72]:35396 "EHLO mail-io1-f72.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229783AbhCEU5R (ORCPT ); Fri, 5 Mar 2021 15:57:17 -0500 Received: by mail-io1-f72.google.com with SMTP id a1so2985730ios.2 for ; Fri, 05 Mar 2021 12:57:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=N9h4PY940X2Vdb/yMG+r/6xuF1LLW6SS3G8crYPx4nQ=; b=EWG+hjVJJgOqHxQvE/o8NYya/+RNhdlezxYiW6eHzuZhaT4ba/rZPT4z3MaGvl32m+ Vkq8ehjfTvx7CE6Hqfwe4sBbVTq7TSHCc7evn9NBASJFIDG4C/mjI73OIHs+8QgxHK3T J8jDzv9bZFC2lU8oOVBNrnPOrPMGtQ/hMEE61DnrpxCtY4qi+nKuBnRfvVDbHfn7mqQN y8I+AeMt7eCMbqH29BzqXt1LlfrK2MDqPNshx3bPcFbEbz2XOZpeby/oB1VzBou90FvH Di0ojBxbfS9181A0Mtds+k9y4s34XtwN0kixaDEa8BCLU/KBHOnmyBXhLALG6Jx7zq5j IuJw== X-Gm-Message-State: AOAM532i+MnUlEwHVTuszYRWWMSRKNoLjRW1fcI82nSEuiejHLOrxAdg f8FzmGz74eJvpFVKdB3Igbf1Vc4z0UCjoJr/TFVGgDWbMo2A X-Google-Smtp-Source: ABdhPJwuPfs/RQ+MRBFmjs3ZlWf8iRxe2qD/yDBCuuDqxnHW2dbFPjBuFTqWJ1MOnaMyxO4SN5g9837J/6kjBjwPuIErJvtY5mtD MIME-Version: 1.0 X-Received: by 2002:a92:da48:: with SMTP id p8mr9941257ilq.137.1614977836989; Fri, 05 Mar 2021 12:57:16 -0800 (PST) Date: Fri, 05 Mar 2021 12:57:16 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000004b43a605bcd0545c@google.com> Subject: [syzbot] net-next boot error: WARNING in kvm_wait From: syzbot To: davem@davemloft.net, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: d310ec03 Merge tag 'perf-core-2021-02-17' of git://git.ker.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=1532e4c6d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=66df2ca4f2dd3022 dashboard link: https://syzkaller.appspot.com/bug?extid=05a8c6cb8281f23c8915 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+05a8c6cb8281f23c8915@syzkaller.appspotmail.com ------------[ cut here ]------------ raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 0 PID: 4818 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: 4818 Comm: selinux-autorel 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: bf ff cc cc cc cc cc cc cc cc cc cc cc 80 3d 8a 88 b1 04 00 74 01 c3 48 c7 c7 40 a2 6b 89 c6 05 79 88 b1 04 01 e8 b8 37 bf 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:ffffc900015cfc40 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffff8be287a0 RCX: 0000000000000000 RDX: ffff888022b31bc0 RSI: ffffffff815b6845 RDI: fffff520002b9f7a RBP: 0000000000000200 R08: 0000000000000000 R09: 0000000000000001 R10: ffffffff815af71e R11: 0000000000000000 R12: 0000000000000003 R13: fffffbfff17c50f4 R14: 0000000000000001 R15: ffff8880b9c35f40 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff7c1ccab04 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:0x7ff7c19e9618 Code: Unable to access opcode bytes at RIP 0x7ff7c19e95ee. RSP: 002b:00007fff88573528 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff7c19e9618 RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 RBP: 000055658b8146e0 R08: 00000000000000e7 R09: ffffffffffffff98 R10: 000055658bead6c0 R11: 0000000000000246 R12: 000055658b8037a0 R13: 00007fff88573810 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 syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.