syzbot


BUG: scheduling while atomic in futex_wait_queue_me (2)

Status: premoderation: reported on 2026/01/25 01:53
Reported-by: syzbot+07675fe8b26ad6ae10fa@syzkaller.appspotmail.com
First crash: 1d13h, last: 1d13h
Similar bugs (4)
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 179d 179d 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 603d 699d 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 180d 180d 0/2 auto-obsoleted due to no activity on 2025/10/27 23:30
android-5-15 BUG: scheduling while atomic in futex_wait_queue_me (3) 5 1 40d 40d 0/2 premoderation: reported on 2025/12/17 13:15

Sample crash report:
erofs: (device loop0): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.0.1969/5742/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8215ca48>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff8215ca48>] z_erofs_reload_indexes+0x318/0x450 fs/erofs/zmap.c:148
CPU: 0 PID: 5742 Comm: syz.0.1969 Tainted: G        W         syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 __dump_stack+0x21/0x24 lib/dump_stack.c:77
 dump_stack_lvl+0x1a7/0x208 lib/dump_stack.c:118
 dump_stack+0x15/0x1c lib/dump_stack.c:135
 __schedule_bug+0x183/0x240 kernel/sched/core.c:4545
 schedule_debug kernel/sched/core.c:4572 [inline]
 __schedule+0xc45/0x1320 kernel/sched/core.c:4700
 schedule+0x13c/0x1d0 kernel/sched/core.c:4884
 freezable_schedule include/linux/freezer.h:197 [inline]
 futex_wait_queue_me+0x29a/0x520 kernel/futex/core.c:2621
 futex_wait+0x269/0x6f0 kernel/futex/core.c:2723
 do_futex+0xfe5/0x1290 kernel/futex/core.c:3757
 __do_sys_futex kernel/futex/core.c:3820 [inline]
 __se_sys_futex+0x2ba/0x370 kernel/futex/core.c:3786
 __x64_sys_futex+0xe5/0x100 kernel/futex/core.c:3786
 do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f9655c6ecb9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f96546cb0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f9655ee9fa8 RCX: 00007f9655c6ecb9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f9655ee9fa8
RBP: 00007f9655ee9fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9655eea038 R14: 00007ffd5bf95660 R15: 00007ffd5bf95748

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/25 01:52 android13-5.10-lts 5601baec60aa 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in futex_wait_queue_me
* Struck through repros no longer work on HEAD.