[Android 5.10] BUG: scheduling while atomic in exit_to_user_mode_loop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e2543346ff7 ANDROID: GKI: Add bpf_redirect_info to virtua..
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=120575f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=78f5b4e6b6dcdd7
dashboard link: https://syzkaller.appspot.com/bug?extid=eb504c1673110fdd427e
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fee170580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122635f4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d6fcf237556b/disk-7e254334.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0bd5e93316ad/vmlinux-7e254334.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1470e1976dee/bzImage-7e254334.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f8b9e27fd275/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=112f5ad4580000)

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

loop0: rw=524288, want=672, limit=16
attempt to access beyond end of device
loop0: rw=524288, want=3670472, limit=16
attempt to access beyond end of device
loop0: rw=524288, want=790384, limit=16
attempt to access beyond end of device
loop0: rw=524288, want=14425508768, limit=16
BUG: scheduling while atomic: syz-executor249/276/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8211ffe0>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff8211ffe0>] z_erofs_reload_indexes+0x1d0/0x450 fs/erofs/zmap.c:132
CPU: 0 PID: 276 Comm: syz-executor249 Not tainted 5.10.237-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
__dump_stack+0x21/0x24 lib/dump_stack.c:77
dump_stack_lvl+0x169/0x1d8 lib/dump_stack.c:118
dump_stack+0x15/0x1c lib/dump_stack.c:135
__schedule_bug+0x177/0x230 kernel/sched/core.c:4545
schedule_debug kernel/sched/core.c:4572 [inline]
__schedule+0xc33/0x1310 kernel/sched/core.c:4700
schedule+0x13c/0x1d0 kernel/sched/core.c:4884
exit_to_user_mode_loop+0x4b/0xe0 kernel/entry/common.c:160
exit_to_user_mode_prepare kernel/entry/common.c:199 [inline]
syscall_exit_to_user_mode+0x68/0x90 kernel/entry/common.c:274
do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fd2464d6739
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 01 1a 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc4ae80358 EFLAGS: 00000246 ORIG_RAX: 00000000000000dd
RAX: 0000000000000000 RBX: 00007fd2465214f4 RCX: 00007fd2464d6739
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fd2465214c4 R08: 0000555500000000 R09: 0000555500000000
R10: 0000000000000003 R11: 0000000000000246 R12: 00007fd24652142c
R13: 0000000000000001 R14: 00007ffc4ae803a0 R15: 0000000000000003
erofs: (device loop0): z_erofs_readpage: failed to read, err [-117]


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