[Android 5.15] BUG: scheduling while atomic in wait_for_common_io (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c85054db4618 Merge 64ee49df839f ("s390/xor: Fix xor_xc_2()..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=120f56ae580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30048ef22650d7ee
dashboard link: https://syzkaller.appspot.com/bug?extid=e571cda6ea17f7d7d0a5
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141aecde580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=160f56ae580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c74b28885c5a/disk-c85054db.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09d149ced009/vmlinux-c85054db.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a0fb16f3ab0e/bzImage-c85054db.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/df1f2877a1d3/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=140f56ae580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e571cd...@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/374/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff822188ec>] kmap_atomic include/linux/highmem-internal.h:196 [inline]
[<ffffffff822188ec>] z_erofs_reload_indexes+0x30c/0x410 fs/erofs/zmap.c:148
CPU: 1 PID: 374 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/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+0xc21/0x14a0 kernel/sched/core.c:6428
schedule+0x11e/0x1e0 kernel/sched/core.c:6621
schedule_timeout+0xba/0x340 kernel/time/timer.c:1898
io_schedule_timeout+0x8d/0x100 kernel/sched/core.c:8655
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common_io+0x16f/0x2e0 kernel/sched/completion.c:123
wait_for_completion_io+0x13/0x20 kernel/sched/completion.c:171
z_erofs_runqueue+0x115d/0x11f0 fs/erofs/zdata.c:1514
z_erofs_readpage+0x25d/0x4d0 fs/erofs/zdata.c:1604
do_read_cache_page+0x58e/0xb10 mm/filemap.c:-1
read_cache_page+0x50/0x70 mm/filemap.c:3676
read_mapping_page include/linux/pagemap.h:513 [inline]
erofs_readdir+0x149/0x8a0 fs/erofs/dir.c:82
iterate_dir+0x25c/0x600 fs/readdir.c:-1
__do_sys_getdents fs/readdir.c:286 [inline]
__se_sys_getdents+0xf2/0x250 fs/readdir.c:271
__x64_sys_getdents+0x7b/0x90 fs/readdir.c:271
x64_sys_call+0xb4/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:79
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:0x7fadb34c3e59
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:00007ffc138406b8 EFLAGS: 00000246 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00007fadb373cfa0 RCX: 00007fadb34c3e59
RDX: 0000000000000058 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fadb3559e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fadb373cfac R14: 00007fadb373cfa0 R15: 00007fadb373cfa0
</TASK>
erofs: (device loop2): z_erofs_readpage: failed to read, err [-117]
erofs: (device loop2): erofs_readdir: fail to readdir of logical block 144 of nid 36


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