syzbot


BUG: scheduling while atomic in futex_wait_queue_me (2)

Status: premoderation: reported on 2025/07/29 23:22
Reported-by: syzbot+39a7dfc9f60364d1a764@syzkaller.appspotmail.com
First crash: 24d, last: 24d
Similar bugs (2)
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 22d 22d 0/2 premoderation: reported on 2025/07/31 10:11
android-5-15 BUG: scheduling while atomic in futex_wait_queue_me 5 19 446d 542d 0/2 auto-obsoleted due to no activity on 2024/08/15 06:55

Sample crash report:
loop2: detected capacity change from 0 to 16
erofs: (device loop2): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.2.178/892/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff821dba10>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff821dba10>] z_erofs_reload_indexes+0x310/0x410 fs/erofs/zmap.c:148
CPU: 0 PID: 892 Comm: syz.2.178 Not tainted 5.15.189-syzkaller-00091-gf32b52534f1d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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:5714
 schedule_debug kernel/sched/core.c:5741 [inline]
 __schedule+0xc2f/0x14c0 kernel/sched/core.c:6409
 schedule+0x11e/0x1e0 kernel/sched/core.c:6602
 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:0x7fa0751259a9
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:00007fa07378e0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fa07534cfa8 RCX: 00007fa0751259a9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fa07534cfa8
RBP: 00007fa07534cfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa07534cfac
R13: 0000000000000000 R14: 00007ffebdd4fac0 R15: 00007ffebdd4fba8
 </TASK>
erofs: (device loop2): z_erofs_readpage: failed to read, err [-117]

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/29 23:21 android13-5.15-lts f32b52534f1d f8f2b4da .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.