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: 24d, last: 9d19h
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 (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in ext4_iomap_begin 1 484d 484d 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 833d 860d 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 408d 523d 25/28 fixed on 2023/12/21 03:45

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5823 at fs/ext4/inode.c:3389 ext4_iomap_begin+0xaa2/0xd30 fs/ext4/inode.c:3389
Modules linked in:
CPU: 0 UID: 0 PID: 5823 Comm: syz-executor562 Not tainted 6.12.0-rc5-syzkaller-00063-g0fc810ae3ae1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
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 48 f2 37 ff 49 be 00 00 00 00 00 fc ff df 48 8b 5c 24 48 e9 61 ff ff ff e8 2f f2 37 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:ffffc90003ee7560 EFLAGS: 00010293
RAX: ffffffff825ce791 RBX: 0000000010000000 RCX: ffff888031505a00
RDX: 0000000000000000 RSI: 00000000000000d4 RDI: 0000000000000000
RBP: ffffc90003ee76d0 R08: ffffffff825cded8 R09: 1ffff1100f18b778
R10: dffffc0000000000 R11: ffffed100f18b779 R12: 00000000000000d4
R13: 1ffff1100f18b7dc R14: 000000000000000a R15: 0000000000000000
FS:  00007f00ef14c6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 0000000077f60000 CR4: 00000000003526f0
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:0x7f00ef195cb9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 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:00007f00ef14c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f00ef21e608 RCX: 00007f00ef195cb9
RDX: 0000000000001006 RSI: 0000000020006c00 RDI: 0000000000000004
RBP: 00007f00ef21e600 R08: 00007f00ef14c6c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f00ef21e60c
R13: 0000000000000006 R14: 00007ffee8483890 R15: 00007ffee8483978
 </TASK>

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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
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
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.