syzbot


WARNING in ext4_iomap_begin (3)

Status: upstream: reported C repro on 2024/10/31 12:34
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+626aa13bf52efc3aa86e@syzkaller.appspotmail.com
First crash: 201d, last: 4h18m
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: kernel BUG in ext4_write_inline_data (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] WARNING in ext4_iomap_begin (3) 0 (2) 2024/11/01 01:18
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in ext4_iomap_begin (2) origin:upstream C 6 1d04h 55d 0/3 upstream: reported C repro on 2025/03/22 23:49
linux-6.1 WARNING in ext4_iomap_begin 1 661d 661d 0/3 auto-obsoleted due to no activity on 2023/11/02 21:33
upstream WARNING in ext4_iomap_begin ext4 C inconclusive error 16 1010d 1037d 0/28 auto-obsoleted due to no activity on 2023/04/04 00:54
upstream WARNING in ext4_iomap_begin (2) ext4 C done 7 585d 700d 25/28 fixed on 2023/12/21 03:45
linux-5.15 WARNING in ext4_iomap_begin origin:upstream C 6 2d14h 10d 0/3 upstream: reported C repro on 2025/05/06 17:05
Last patch testing requests (7)
Created Duration User Patch Repo Result
2025/04/06 03:10 14m retest repro upstream report log
2025/03/10 06:34 15m retest repro upstream report log
2025/02/14 09:42 13m retest repro upstream report log
2025/02/14 09:42 13m retest repro upstream report log
2024/12/06 06:18 15m retest repro upstream report log
2024/12/06 06:18 16m retest repro upstream report log
2024/12/06 06:18 1h09m retest repro upstream report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/01/25 21:26 2h52m bisect fix upstream OK (0) job log log

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5836 at fs/ext4/inode.c:3414 ext4_iomap_begin+0xab5/0xd50 fs/ext4/inode.c:3414
Modules linked in:
CPU: 1 UID: 0 PID: 5836 Comm: syz-executor405 Not tainted 6.15.0-rc1-syzkaller-00288-ge618ee89561b #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:ext4_iomap_begin+0xab5/0xd50 fs/ext4/inode.c:3414
Code: cc cc cc cc e8 8c cd 41 ff 49 c7 c7 20 70 65 93 49 be 00 00 00 00 00 fc ff df 48 8b 5c 24 48 e9 5f ff ff ff e8 6c cd 41 ff 90 <0f> 0b 90 41 bc de ff ff ff e9 76 f6 ff ff 89 d9 80 e1 07 38 c1 0f
RSP: 0018:ffffc9000411f4a0 EFLAGS: 00010293
RAX: ffffffff82817704 RBX: 0000000010000000 RCX: ffff888034768000
RDX: 0000000000000000 RSI: 00000000000000d4 RDI: 0000000000000000
RBP: ffffc9000411f610 R08: ffffffff82816e41 R09: 1ffff1100f067c6c
R10: dffffc0000000000 R11: ffffed100f067c6d R12: 00000000000000d4
R13: 1ffff1100f067cd8 R14: 000000000000000a R15: 0000000000000000
FS:  00007fb0ef7146c0(0000) GS:ffff8881250c9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb0ef713f80 CR3: 0000000075628000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 iomap_iter+0x50b/0xe10 fs/iomap/iter.c:109
 __iomap_dio_rw+0xdf8/0x24f0 fs/iomap/direct-io.c:733
 iomap_dio_rw+0x46/0xa0 fs/iomap/direct-io.c:823
 ext4_dio_write_iter fs/ext4/file.c:575 [inline]
 ext4_file_write_iter+0x18d8/0x1da0 fs/ext4/file.c:716
 new_sync_write fs/read_write.c:591 [inline]
 vfs_write+0x70f/0xd10 fs/read_write.c:684
 ksys_write+0x19d/0x2d0 fs/read_write.c:736
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb0ef7a2259
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 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:00007fb0ef714168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fb0ef8296e8 RCX: 00007fb0ef7a2259
RDX: 0000000000002400 RSI: 0000200000000000 RDI: 0000000000000004
RBP: 00007fb0ef8296e0 R08: 00007fb0ef8296e0 R09: 0000000000000000
R10: 00007fb0ef714170 R11: 0000000000000246 R12: 00007fb0ef8296ec
R13: 000000000000006e R14: 00007ffee8309580 R15: 00007ffee8309668
 </TASK>

Crashes (34):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/12 05:16 upstream e618ee89561b 0bd6db41 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/01 01:17 upstream 0fc810ae3ae1 96eb609f .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/02/23 20:33 upstream 27102b38b8ca d34966d1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root WARNING in ext4_iomap_begin
2025/05/07 12:37 upstream 0d8d44db295c 350f4ffc .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/11 10:59 upstream 2d5404caa8c7 0c4b1325 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/11 07:31 upstream a9cda7c0ffed 6b856513 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/17 02:52 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/16 14:37 upstream fee3e843b309 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/16 07:39 upstream fee3e843b309 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/14 21:56 upstream 9f35e33144ae a4fa04ef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in ext4_iomap_begin
2025/05/14 19:29 upstream 9f35e33144ae a4fa04ef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in ext4_iomap_begin
2025/05/14 19:24 upstream 9f35e33144ae a4fa04ef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in ext4_iomap_begin
2025/05/08 05:47 upstream 707df3375124 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/08 04:11 upstream 707df3375124 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/05/07 04:38 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/04/22 05:06 upstream a33b5a08cbbd 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/04/22 05:04 upstream a33b5a08cbbd 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/04/19 01:39 upstream fc96b232f8e7 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/04/15 00:35 upstream 834a4a689699 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/02/24 06:29 upstream d082ecbc71e9 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/12/15 05:08 upstream a0e3919a2df2 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/12/13 00:24 upstream 150b567e0d57 530e80f8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/12/08 03:52 upstream 7503345ac5f5 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/12/06 18:17 upstream b8f52214c61a 946d28f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/22 02:09 upstream 43fb83c17ba2 4b25d554 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/11 09:22 upstream 2d5404caa8c7 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/11 07:00 upstream a9cda7c0ffed 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/03 23:38 upstream a33ab3f94f51 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/02 20:43 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/02 13:25 upstream 11066801dd4b f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/01 21:51 upstream 6c52d4da1c74 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2024/11/01 00:18 upstream 0fc810ae3ae1 96eb609f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_iomap_begin
2025/04/29 19:30 upstream ca91b9500108 9e704644 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in ext4_iomap_begin
2024/10/27 12:28 upstream 850925a8133c 65e8686b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in ext4_iomap_begin
* Struck through repros no longer work on HEAD.