Hello, syzbot found the following issue on: HEAD commit: 850925a8133c Merge tag '9p-for-6.12-rc5' of https://github.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=109c2940580000 kernel config: https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28 dashboard link: https://syzkaller.appspot.com/bug?extid=626aa13bf52efc3aa86e 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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-850925a8.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c831c931f29c/vmlinux-850925a8.xz kernel image: https://storage.googleapis.com/syzbot-assets/85f584e52a7f/bzImage-850925a8.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+626aa13bf52efc3aa86e@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5328 at fs/ext4/inode.c:3389 ext4_iomap_begin+0xaa2/0xd30 fs/ext4/inode.c:3389 Modules linked in: CPU: 0 UID: 0 PID: 5328 Comm: syz.0.0 Not tainted 6.12.0-rc4-syzkaller-00261-g850925a8133c #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:ext4_iomap_begin+0xaa2/0xd30 fs/ext4/inode.c:3389 Code: 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 18 ce 34 ff 49 be 00 00 00 00 00 fc ff df 48 8b 5c 24 48 e9 61 ff ff ff e8 ff cd 34 ff 90 <0f> 0b 90 41 bc de ff ff ff e9 87 f6 ff ff 89 d9 80 e1 07 38 c1 0f RSP: 0018:ffffc9000d087560 EFLAGS: 00010293 RAX: ffffffff82601c71 RBX: 0000000010000000 RCX: ffff888000bb8000 RDX: 0000000000000000 RSI: 00000000000000d4 RDI: 0000000000000000 RBP: ffffc9000d0876d0 R08: ffffffff826013b8 R09: 1ffff110087be63b R10: dffffc0000000000 R11: ffffed10087be63c R12: 00000000000000d4 R13: 1ffff110087be69f R14: 000000000000000b R15: 0000000000000000 FS: 00007fbf155ff6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fbf09d45000 CR3: 0000000042eb6000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> iomap_iter+0x691/0xf60 fs/iomap/iter.c:91 __iomap_dio_rw+0xdea/0x2370 fs/iomap/direct-io.c:677 iomap_dio_rw+0x46/0xa0 fs/iomap/direct-io.c:767 ext4_dio_write_iter fs/ext4/file.c:577 [inline] ext4_file_write_iter+0x15f0/0x1a20 fs/ext4/file.c:696 new_sync_write fs/read_write.c:590 [inline] vfs_write+0xaeb/0xd30 fs/read_write.c:683 ksys_write+0x183/0x2b0 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fbf1577e719 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fbf155ff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fbf15936130 RCX: 00007fbf1577e719 RDX: 000000000000001c RSI: 0000000020000300 RDI: 0000000000000007 RBP: 00007fbf157f132e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000001 R14: 00007fbf15936130 R15: 00007ffd4ab6bf78 </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 syzkaller@xxxxxxxxxxxxxxxx. 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
