[Android 5.15] BUG: scheduling while atomic in futex_wait_queue_me (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e1070528954 Merge android13-5.15 into android13-5.15-lts
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=10d9aa5a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=deffac0a782f1cb0
dashboard link: https://syzkaller.appspot.com/bug?extid=e3cd2a46eac8b4982da4
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c38b22580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=107e47fa580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6895df5d7496/disk-7e107052.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/153bd31b2719/vmlinux-7e107052.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d9e2a19c0f4f/bzImage-7e107052.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a0147f6eb4f4/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16480a52580000)

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

loop2: detected capacity change from 0 to 16
erofs: (device loop2): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.2.17/373/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff82216af0>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff82216af0>] z_erofs_reload_indexes+0x310/0x410 fs/erofs/zmap.c:148
CPU: 0 PID: 373 Comm: syz.2.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+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:3995
__do_sys_futex kernel/futex/core.c:4072 [inline]
__se_sys_futex+0x135/0x330 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:0x7f4746723eb9
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:00007f47465880e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f474699efa8 RCX: 00007f4746723eb9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f474699efa8
RBP: 00007f474699efa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f474699f038 R14: 00007fffe3b0aae0 R15: 00007fffe3b0abc8
</TASK>


---
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 syzk...@googlegroups.com.

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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup