syzbot


BUG: scheduling while atomic in futex_wait_queue_me (3)

Status: premoderation: reported on 2025/12/17 13:15
Reported-by: syzbot+9230bde2000ff808c02c@syzkaller.appspotmail.com
First crash: 2d06h, last: 2d06h
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 BUG: scheduling while atomic in futex_wait_queue_me 5 1 141d 141d 0/2 auto-obsoleted due to no activity on 2025/10/29 10:17
android-5-15 BUG: scheduling while atomic in futex_wait_queue_me 5 19 565d 661d 0/2 auto-obsoleted due to no activity on 2024/08/15 06:55
android-5-15 BUG: scheduling while atomic in futex_wait_queue_me (2) 5 1 142d 142d 0/2 auto-obsoleted due to no activity on 2025/10/27 23:30

Sample crash report:
loop4: detected capacity change from 0 to 16
erofs: (device loop4): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.4.17/371/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff821df410>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff821df410>] z_erofs_reload_indexes+0x310/0x410 fs/erofs/zmap.c:148
CPU: 1 PID: 371 Comm: syz.4.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 __dump_stack+0x21/0x30 lib/dump_stack.c:88
 dump_stack_lvl+0xee/0x150 lib/dump_stack.c:106
 dump_stack+0x15/0x20 lib/dump_stack.c:113
 __schedule_bug+0x174/0x230 kernel/sched/core.c:5733
 schedule_debug kernel/sched/core.c:5760 [inline]
 __schedule+0xc2f/0x14c0 kernel/sched/core.c:6428
 schedule+0x11e/0x1e0 kernel/sched/core.c:6621
 freezable_schedule include/linux/freezer.h:197 [inline]
 futex_wait_queue_me+0x28a/0x650 kernel/futex/core.c:2872
 futex_wait+0x211/0x810 kernel/futex/core.c:2975
 do_futex+0xcb2/0x2620 kernel/futex/core.c:3995
 __do_sys_futex kernel/futex/core.c:4072 [inline]
 __se_sys_futex+0x139/0x310 kernel/futex/core.c:4053
 __x64_sys_futex+0xe5/0x100 kernel/futex/core.c:4053
 x64_sys_call+0x251/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:203
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f60313b5749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f602fe1d0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f603160bfa8 RCX: 00007f60313b5749
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f603160bfa8
RBP: 00007f603160bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f603160c038 R14: 00007ffea5916920 R15: 00007ffea5916a08
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/17 13:14 android13-5.15-lts 050dc55b0457 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
* Struck through repros no longer work on HEAD.