[Android 5.10] BUG: scheduling while atomic in wait_on_page_bit_common

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 50b3a256e550 Merge 5.10.260 into android13-5.10-lts
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=15297c32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57bdfa4a173e5087
dashboard link: https://syzkaller.appspot.com/bug?extid=29e5c722420f194db5db
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104e8ab9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168c12b9580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/34994db436ce/disk-50b3a256.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7855257a6b73/vmlinux-50b3a256.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6367ad2e120a/bzImage-50b3a256.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/cf7cb6189fe3/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=128c12b9580000)

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

erofs: (device loop2): mounted with root inode @ nid 36.
erofs: (device loop2): z_erofs_readahead: readahead error at page 6 @ nid 89
erofs: (device loop2): z_erofs_readahead: readahead error at page 5 @ nid 89
erofs: (device loop2): z_erofs_readahead: readahead error at page 4 @ nid 89
erofs: (device loop2): z_erofs_readahead: readahead error at page 3 @ nid 89
erofs: (device loop2): z_erofs_readahead: readahead error at page 2 @ nid 89
erofs: (device loop2): z_erofs_get_extent_compressedlen: cannot found CBLKCNT @ lcn 1 of nid 89
erofs: (device loop2): z_erofs_readahead: readahead error at page 1 @ nid 89
BUG: scheduling while atomic: syz.2.17/391/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8215939c>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff8215939c>] z_erofs_reload_indexes+0x1cc/0x450 fs/erofs/zmap.c:132
CPU: 0 PID: 391 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
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+0xcee/0x13e0 kernel/sched/core.c:4700
schedule+0x13c/0x1d0 kernel/sched/core.c:4884
io_schedule+0x84/0xe0 kernel/sched/core.c:6593
wait_on_page_bit_common+0x812/0xa80 mm/filemap.c:1282
wait_on_page_bit_killable mm/filemap.c:1350 [inline]
wait_on_page_locked_killable include/linux/pagemap.h:679 [inline]
generic_file_buffered_read+0x92b/0x26d0 mm/filemap.c:2284
generic_file_read_iter+0x10b/0x580 mm/filemap.c:2568
call_read_iter include/linux/fs.h:2060 [inline]
new_sync_read fs/read_write.c:415 [inline]
vfs_read+0x62a/0xa50 fs/read_write.c:496
ksys_read+0x14a/0x260 fs/read_write.c:634
__do_sys_read fs/read_write.c:644 [inline]
__se_sys_read fs/read_write.c:642 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:642
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3d87319e99
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:00007ffed44fdc88 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f3d875a1fa0 RCX: 00007f3d87319e99
RDX: 0000000000002020 RSI: 0000200000000940 RDI: 0000000000000004
RBP: 00007f3d873afeaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3d875a1fac R14: 00007f3d875a1fa0 R15: 00007f3d875a1fa0


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