linux-kernel - [syzbot] BUG: scheduling while atomic in exit_to_user_mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <000000000000d5e6b605e1df63be@google.com>
Date:   Mon, 20 Jun 2022 04:27:32 -0700
From:   syzbot <syzbot+0b658e1b540fcfc0be70@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, luto@...nel.org,
        peterz@...radead.org, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de
Subject: [syzbot] BUG: scheduling while atomic in exit_to_user_mode_prepare

Hello,

syzbot found the following issue on:

HEAD commit:    6012273897fe Add linux-next specific files for 20220615
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1584bc0ff00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b4154677977b1776
dashboard link: https://syzkaller.appspot.com/bug?extid=0b658e1b540fcfc0be70
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0b658e1b540fcfc0be70@...kaller.appspotmail.com

BUG: scheduling while atomic: syz-executor.3/16818/0x00000002
no locks held by syz-executor.3/16818.
Modules linked in:
Preemption disabled at:
[<ffffffff81bc96e5>] rmqueue_pcplist mm/page_alloc.c:3813 [inline]
[<ffffffff81bc96e5>] rmqueue mm/page_alloc.c:3858 [inline]
[<ffffffff81bc96e5>] get_page_from_freelist+0x455/0x3a20 mm/page_alloc.c:4293
Kernel panic - not syncing: scheduling while atomic
CPU: 1 PID: 16818 Comm: syz-executor.3 Not tainted 5.19.0-rc2-next-20220615-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 panic+0x2d7/0x636 kernel/panic.c:274
 __schedule_bug.cold+0x10c/0x143 kernel/sched/core.c:5690
 schedule_debug kernel/sched/core.c:5719 [inline]
 __schedule+0x31a8/0x4c00 kernel/sched/core.c:6354
 schedule+0xd2/0x1f0 kernel/sched/core.c:6532
 exit_to_user_mode_loop kernel/entry/common.c:157 [inline]
 exit_to_user_mode_prepare+0x142/0x250 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294
 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7f6012689152
Code: 00 00 00 00 00 0f 1f 00 41 f7 c1 ff 0f 00 00 75 27 55 48 89 fd 53 89 cb 48 85 ff 74 3b 41 89 da 48 89 ef b8 09 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 66 5b 5d c3 0f 1f 00 48 c7 c0 b8 ff ff ff 64
RSP: 002b:00007ffd01d6ca18 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: 00007f60137cb000 RBX: 0000000000020022 RCX: 00007f6012689152
RDX: 0000000000000000 RSI: 0000000000021000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000020022 R11: 0000000000000246 R12: 00007ffd01d6cc20
R13: 00007f6011dff700 R14: 0000000000000000 R15: 0000000000022000
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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@...glegroups.com.

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