[Android 5.10] BUG: scheduling while atomic in futex_wait_queue_me (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 58c592510fcd Merge 5.10.248 into android13-5.10-lts
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=144c17fa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef167f989dba92e
dashboard link: https://syzkaller.appspot.com/bug?extid=1b7a4327d7d52f62f4ac
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=1421eb22580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1675865a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5f658524a370/disk-58c59251.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef9f5387b57b/vmlinux-58c59251.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e1f18f7534a/bzImage-58c59251.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/000176699f81/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1275865a580000)

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

erofs: (device loop2): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.2.17/390/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8215ca78>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff8215ca78>] z_erofs_reload_indexes+0x318/0x450 fs/erofs/zmap.c:148
CPU: 1 PID: 390 Comm: syz.2.17 Not tainted 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:0x7ff69e718eb9
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:00007ff69e57d0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007ff69e993fa8 RCX: 00007ff69e718eb9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007ff69e993fa8
RBP: 00007ff69e993fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff69e994038 R14: 00007ffc878db910 R15: 00007ffc878db9f8


---
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