syzbot


WARNING in ext4_iomap_begin (2)

Status: upstream: reported C repro on 2025/08/11 00:02
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+8ebd9f6d0fb9a8248a5f@syzkaller.appspotmail.com
First crash: 10d, last: 11h43m
Bug presence (1)
Date Name Commit Repro Result
2025/08/15 upstream (ToT) d0efc9e4276c C [report] WARNING in ext4_iomap_begin
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in ext4_iomap_begin (2) origin:upstream -1 C done 10 65d 150d 3/3 fixed on 2025/07/16 19:57
linux-6.1 WARNING in ext4_iomap_begin -1 1 756d 756d 0/3 auto-obsoleted due to no activity on 2023/11/02 21:33
upstream WARNING in ext4_iomap_begin ext4 -1 C inconclusive error 16 1105d 1133d 0/29 auto-obsoleted due to no activity on 2023/04/04 00:54
upstream WARNING in ext4_iomap_begin (2) ext4 -1 C done 7 681d 795d 25/29 fixed on 2023/12/21 03:45
linux-5.15 WARNING in ext4_iomap_begin origin:upstream -1 C done 8 72d 106d 3/3 fixed on 2025/07/14 10:31
upstream WARNING in ext4_iomap_begin (3) ext4 -1 C inconclusive 62 1d18h 293d 0/29 upstream: reported C repro on 2024/10/31 12:34

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5068 at fs/ext4/inode.c:3436 ext4_iomap_begin+0xa0d/0xb80 fs/ext4/inode.c:3436
Modules linked in:
CPU: 0 PID: 5068 Comm: syz.4.161 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ext4_iomap_begin+0xa0d/0xb80 fs/ext4/inode.c:3436
Code: 89 e8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 87 fd 6f ff 48 bb 00 00 00 00 00 fc ff df e9 71 ff ff ff e8 73 fd 6f ff <0f> 0b 41 bd de ff ff ff 48 bb 00 00 00 00 00 fc ff df e9 7b ff ff
RSP: 0000:ffffc90005627600 EFLAGS: 00010293
RAX: ffffffff8207c6ad RBX: ffff88805945175a RCX: ffff8880259f0000
RDX: 0000000000000000 RSI: 00000000000000d4 RDI: 0000000000000000
RBP: ffffc90005627780 R08: dffffc0000000000 R09: ffffed100b28a289
R10: ffffed100b28a289 R11: 1ffff1100b28a288 R12: 00000000000000d4
R13: 1ffff1100b28a2eb R14: 000000000000000b R15: 0000000000000000
FS:  00007f9a4eba36c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000880 CR3: 000000005dca7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 iomap_iter+0x620/0xdb0 fs/iomap/iter.c:74
 __iomap_dio_rw+0xa69/0x1a70 fs/iomap/direct-io.c:585
 iomap_dio_rw+0x38/0x90 fs/iomap/direct-io.c:672
 ext4_dio_write_iter fs/ext4/file.c:540 [inline]
 ext4_file_write_iter+0x132b/0x17b0 fs/ext4/file.c:660
 call_write_iter include/linux/fs.h:2172 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x712/0xd00 fs/read_write.c:594
 ksys_pwrite64 fs/read_write.c:701 [inline]
 __do_sys_pwrite64 fs/read_write.c:711 [inline]
 __se_sys_pwrite64 fs/read_write.c:708 [inline]
 __x64_sys_pwrite64+0x194/0x220 fs/read_write.c:708
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f9a4f533be9
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:00007f9a4eba3038 EFLAGS: 00000246 ORIG_RAX: 0000000000000012
RAX: ffffffffffffffda RBX: 00007f9a4f75afa0 RCX: 00007f9a4f533be9
RDX: 0000000000000001 RSI: 0000200000000880 RDI: 0000000000000006
RBP: 00007f9a4f5b6e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000083 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9a4f75b038 R14: 00007f9a4f75afa0 R15: 00007ffeddf38178
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/11 04:51 linux-5.15.y c79648372d02 32a0e5ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/11 03:28 linux-5.15.y c79648372d02 32a0e5ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/11 00:04 linux-5.15.y c79648372d02 32a0e5ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/10 22:24 linux-5.15.y c79648372d02 32a0e5ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/11 06:03 linux-5.15.y c79648372d02 32a0e5ed .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/20 09:38 linux-5.15.y c79648372d02 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
2025/08/10 20:45 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in ext4_iomap_begin
* Struck through repros no longer work on HEAD.