[v6.1] WARNING in iomap_iter

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5cd595e23c1 Linux 6.1.83
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11e7ffe6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=99d0cbbc2b2c7cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=016d861797fd718491a8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cd28292a2eef/disk-e5cd595e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8297fd856b2/vmlinux-e5cd595e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ea8c74634429/bzImage-e5cd595e.xz

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

erofs: (device loop3): z_erofs_pcluster_readmore: readmore error at page 0 @ nid 36
erofs: (device loop3): z_erofs_read_folio: failed to read, err [-117]
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3759 at fs/iomap/iter.c:35 iomap_iter+0x978/0xfc0 fs/iomap/iter.c:78
Modules linked in:
CPU: 0 PID: 3759 Comm: syz-executor.3 Not tainted 6.1.83-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:iomap_iter_done fs/iomap/iter.c:35 [inline]
RIP: 0010:iomap_iter+0x978/0xfc0 fs/iomap/iter.c:78
Code: ff e8 1c 01 7b ff 0f 0b e9 d5 f9 ff ff e8 10 01 7b ff 0f 0b e9 58 fd ff ff e8 04 01 7b ff 0f 0b e9 8a fd ff ff e8 f8 00 7b ff <0f> 0b e9 ee fd ff ff e8 ec 00 7b ff 0f 0b e9 3d fe ff ff e8 e0 00
RSP: 0018:ffffc90004897830 EFLAGS: 00010283
RAX: ffffffff820f83f8 RBX: 000000000a001000 RCX: 0000000000040000
RDX: ffffc9000a90a000 RSI: 000000000000085a RDI: 000000000000085b
RBP: 06cc00000a000000 R08: ffffffff820f81df R09: fffff940002cb69f
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000912f2c
R13: 1ffff92000912f32 R14: 1ffff92000912f2d R15: dffffc0000000000
FS: 00007f83459a36c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020065000 CR3: 000000005d30b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
iomap_fiemap+0x1c9/0x960 fs/iomap/fiemap.c:80
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x18e9/0x2a90 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f8344c7dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f83459a30c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8344dabf80 RCX: 00007f8344c7dda9
RDX: 0000000020000200 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f8344cca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8344dabf80 R15: 00007ffd85aeae18
</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 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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e5cd595e23c1 Linux 6.1.83
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=176139b1180000

kernel config: https://syzkaller.appspot.com/x/.config?x=99d0cbbc2b2c7cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=016d861797fd718491a8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d15795180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c5ccc5180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cd28292a2eef/disk-e5cd595e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8297fd856b2/vmlinux-e5cd595e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ea8c74634429/bzImage-e5cd595e.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/bac04f14bc8f/mount_0.gz

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

loop0: detected capacity change from 0 to 16
erofs: (device loop0): mounted with root inode @ nid 36.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3539 at fs/iomap/iter.c:35 iomap_iter+0x978/0xfc0 fs/iomap/iter.c:78
Modules linked in:
CPU: 1 PID: 3539 Comm: syz-executor328 Not tainted 6.1.83-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:iomap_iter_done fs/iomap/iter.c:35 [inline]
RIP: 0010:iomap_iter+0x978/0xfc0 fs/iomap/iter.c:78
Code: ff e8 1c 01 7b ff 0f 0b e9 d5 f9 ff ff e8 10 01 7b ff 0f 0b e9 58 fd ff ff e8 04 01 7b ff 0f 0b e9 8a fd ff ff e8 f8 00 7b ff <0f> 0b e9 ee fd ff ff e8 ec 00 7b ff 0f 0b e9 3d fe ff ff e8 e0 00

RSP: 0018:ffffc900039cf830 EFLAGS: 00010293
RAX: ffffffff820f83f8 RBX: 000000000a001000 RCX: ffff8880272f0000
RDX: 0000000000000000 RSI: 06cc00000a000000 RDI: 000000000a001000
RBP: 06cc00000a000000 R08: ffffffff820f81df R09: fffff940003ce607
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000739f2c
R13: 1ffff92000739f32 R14: 1ffff92000739f2d R15: dffffc0000000000
FS: 0000555556165380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007ffdbe325000 CR3: 000000007b26b000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
iomap_fiemap+0x1c9/0x960 fs/iomap/fiemap.c:80
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x18e9/0x2a90 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd

RIP: 0033:0x7f5dd5644639
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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:00007ffdbe324188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffdbe324358 RCX: 00007f5dd5644639

RDX: 0000000020000200 RSI: 00000000c020660b RDI: 0000000000000004

RBP: 00007f5dd56b7610 R08: 0000000000000000 R09: 00007ffdbe324358
R10: 00000000000001f0 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffdbe324348 R14: 0000000000000001 R15: 0000000000000001
</TASK>


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