[v6.1] WARNING in ext4_iomap_begin

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5302e81aa209 Linux 6.1.41
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17e660d9a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=773f0dbbc4999ad5
dashboard link: https://syzkaller.appspot.com/bug?extid=50b971fcb9b57dc5a12a
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/0d4c5b598789/disk-5302e81a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e6fc722fbbe4/vmlinux-5302e81a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a18ebb82b176/bzImage-5302e81a.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7149 at fs/ext4/inode.c:3442 ext4_iomap_begin+0xa8f/0xd20
Modules linked in:
CPU: 1 PID: 7149 Comm: syz-executor.4 Not tainted 6.1.41-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:ext4_iomap_begin+0xa8f/0xd20 fs/ext4/inode.c:3442
Code: d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 aa 8b 52 ff 49 be 00 00 00 00 00 fc ff df 48 8b 5c 24 48 e9 65 ff ff ff e8 91 8b 52 ff <0f> 0b 41 bc de ff ff ff e9 97 f6 ff ff 89 d9 80 e1 07 38 c1 0f 8c
RSP: 0018:ffffc9000c367300 EFLAGS: 00010287
RAX: ffffffff82374f5f RBX: 0000000010000000 RCX: 0000000000040000
RDX: ffffc9000cba2000 RSI: 00000000000205ed RDI: 00000000000205ee
RBP: ffffc9000c367480 R08: ffffffff823746b4 R09: ffffed100dfe4dd6
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000000000a4
R13: 1ffff1100dfe4e3a R14: 000000000000000b R15: 0000000000000080
FS: 00007f7f345c26c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4a3167c0d0 CR3: 0000000080e41000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
iomap_iter+0x642/0xfc0 fs/iomap/iter.c:74
__iomap_dio_rw+0xdff/0x2240 fs/iomap/direct-io.c:601
iomap_dio_rw+0x42/0xa0 fs/iomap/direct-io.c:690
ext4_dio_read_iter fs/ext4/file.c:94 [inline]
ext4_file_read_iter+0x50b/0x660 fs/ext4/file.c:145
call_read_iter include/linux/fs.h:2199 [inline]
generic_file_splice_read+0x23c/0x630 fs/splice.c:309
do_splice_to fs/splice.c:793 [inline]
splice_direct_to_actor+0x408/0xbd0 fs/splice.c:865
do_splice_direct+0x27f/0x3c0 fs/splice.c:974
do_sendfile+0x61c/0xff0 fs/read_write.c:1255
__do_sys_sendfile64 fs/read_write.c:1323 [inline]
__se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1309
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7f3387cb29
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:00007f7f345c20c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f7f3399bf80 RCX: 00007f7f3387cb29
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000006
RBP: 00007f7f338c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f7f3399bf80 R15: 00007ffe0dd18068
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.