BUG: scheduling while atomic in futex_wait_queue_me (3)

Status: upstream: reported C repro on 2026/02/04 23:24
Bug presence: origin:downstream
[Documentation on labels]
Reported-by: syzbot+e3cd2a46eac8b4982da4@syzkaller.appspotmail.com
First crash: 231d, last: 74d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Bug presence (3)
Date Name Commit Repro Result
2026/02/05 android13-5.15-lts (ToT) 7e1070528954 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2026/02/05 lts (merge base) 278455a82245 C Didn't crash
2026/02/05 upstream (ToT) f14faaf3a1fb C Didn't crash
▶ ▼ 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 370d 370d 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 794d 890d 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 371d 371d 0/2 auto-obsoleted due to no activity on 2025/10/27 23:30
android-5-10 BUG: scheduling while atomic in futex_wait_queue_me (2) 5 syz, C error 11 2h57m 177d 0/2 upstream: reported C repro on 2026/02/09 01:36
▶ ▼ Last patch testing requests (5)
Created Duration User Patch Repo Result
2026/06/07 16:08 13m retest repro android13-5.15-lts log
2026/06/07 16:08 13m retest repro android13-5.15-lts log
2026/06/07 16:08 21m retest repro android13-5.15-lts log
2026/06/07 16:08 19m retest repro android13-5.15-lts log
2026/06/07 16:08 23m retest repro android13-5.15-lts log

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.17/374/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff82218c90>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff82218c90>] z_erofs_reload_indexes+0x310/0x410 fs/erofs/zmap.c:148
CPU: 0 PID: 374 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 __dump_stack+0x21/0x30 lib/dump_stack.c:88
 dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
 dump_stack+0x15/0x20 lib/dump_stack.c:113
 __schedule_bug+0x180/0x230 kernel/sched/core.c:5733
 schedule_debug kernel/sched/core.c:5760 [inline]
 __schedule+0xc30/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+0x29c/0x660 kernel/futex/core.c:2872
 futex_wait+0x258/0x8f0 kernel/futex/core.c:2975
 do_futex+0xdc6/0x2800 kernel/futex/core.c:3996
 __do_sys_futex kernel/futex/core.c:4073 [inline]
 __se_sys_futex+0x135/0x330 kernel/futex/core.c:4054
 __x64_sys_futex+0xe5/0x100 kernel/futex/core.c:4054
 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:0x7f672b762e59
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:00007f672b5c50e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f672b9dbfa8 RCX: 00007f672b762e59
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f672b9dbfa8
RBP: 00007f672b9dbfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f672b9dc038 R14: 00007ffd899cfca0 R15: 00007ffd899cfd88
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/22 18:00 android13-5.15-lts 05eea940894a 5f091fcc .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
2026/05/22 09:45 android13-5.15-lts 05eea940894a 70ae9b03 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
2026/05/20 22:57 android13-5.15-lts 05eea940894a 62fb93a2 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
2026/02/04 23:19 android13-5.15-lts 7e1070528954 ea10c935 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
2026/05/21 06:27 android13-5.15-lts 05eea940894a 41b8c833 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
2026/01/26 20:20 android13-5.15-lts fd7f3945989f a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in futex_wait_queue_me
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.