syzbot

 sign-in | mailing list | source | docs
🐞 Open [124]
🐞 Fixed [70]
🐞 Invalid [218]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

kernel BUG in ext4_split_extent_at

Status: upstream: reported C repro on 2023/06/09 00:07
Reported-by: syzbot+1257631df4d42447d768@syzkaller.appspotmail.com
First crash: 958d, last: 13h51m
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG in ext4_split_extent_at ext4 1 1231d 1226d 0/29 auto-closed as invalid on 2022/06/08 01:32
upstream kernel BUG in ext4_split_extent_at (2) ext4 C error done 3 546d 741d 25/29 fixed on 2024/01/30 15:47
android-6-1 kernel BUG in ext4_split_extent_at missing-backport origin:upstream C error error 1 283d 745d 0/2 auto-obsoleted due to no activity on 2024/12/21 09:12
android-5-15 kernel BUG in ext4_split_extent_at missing-backport origin:lts C error error 2 5d20h 25d 0/2 upstream: reported C repro on 2025/05/29 02:28
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/05/28 09:21 7m retest repro android13-5.10-lts report log
2025/05/28 09:21 9m retest repro android13-5.10-lts report log
2025/05/28 09:21 6m retest repro android13-5.10-lts report log
2025/05/12 22:24 28m retest repro android13-5.10-lts report log
2025/05/12 22:24 11m retest repro android13-5.10-lts report log
2025/04/16 00:38 12m retest repro android13-5.10-lts report log
2025/03/13 07:05 7m retest repro android13-5.10-lts report log
2025/03/13 07:05 9m retest repro android13-5.10-lts report log
2025/03/13 07:05 5m retest repro android13-5.10-lts report log
2025/02/26 14:02 7m retest repro android13-5.10-lts report log

Sample crash report:
EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue
ext4 filesystem being mounted at /file0 supports timestamps until 2038-01-19 (0x7fffffff)
EXT4-fs error (device loop0): ext4_xattr_block_get:546: inode #15: comm syz-executor181: corrupted xattr block 19
------------[ cut here ]------------
kernel BUG at fs/ext4/extents.c:3180!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 291 Comm: syz-executor181 Not tainted 5.10.234-syzkaller-00033-g094fc3778d6b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:ext4_split_extent_at+0x121c/0x1240 fs/ext4/extents.c:3180
Code: fe c1 38 c1 0f 8c 16 fa ff ff e8 cf b7 cf ff 48 8b 54 24 58 48 8b 74 24 40 e9 02 fa ff ff e8 1b 18 92 ff 0f 0b e8 14 18 92 ff <0f> 0b e8 0d 18 92 ff 0f 0b e8 66 4f d5 02 e8 01 18 92 ff 0f 0b e8
RSP: 0018:ffffc90000b57820 EFLAGS: 00010293
RAX: ffffffff81d8a73c RBX: 0000000000000000 RCX: ffff88810d0e13c0
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000000000000000
RBP: ffffc90000b57990 R08: ffffffff81d897a2 R09: ffffc90000b57920
R10: fffff5200016af25 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 1ffff110226b35ff R15: 0000000000000000
FS:  00007f43d63ae6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000020000 CR3: 000000010b9fc000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 ext4_force_split_extent_at fs/ext4/extents.c:318 [inline]
 ext4_ext_remove_space+0x719/0x4e10 fs/ext4/extents.c:2873
 ext4_punch_hole+0x720/0xb10 fs/ext4/inode.c:4216
 ext4_fallocate+0x2e8/0x1cc0 fs/ext4/extents.c:4756
 vfs_fallocate+0x492/0x570 fs/open.c:310
 ksys_fallocate fs/open.c:333 [inline]
 __do_sys_fallocate fs/open.c:341 [inline]
 __se_sys_fallocate fs/open.c:339 [inline]
 __x64_sys_fallocate+0xc0/0x110 fs/open.c:339
 do_syscall_64+0x34/0x70 arch/x86/entry/common.c:-1
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f43d63fe019
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 1f 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:00007f43d63ae168 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f43d64916e8 RCX: 00007f43d63fe019
RDX: 0000000000000004 RSI: 0000000000000003 RDI: 0000000000000004
RBP: 00007f43d64916e0 R08: 00007f43d63ae6c0 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 00007f43d64916ec
R13: 0000000000000010 R14: 00007ffdc576fa50 R15: 00007ffdc576fb38
Modules linked in:
---[ end trace 93128771453386ff ]---
RIP: 0010:ext4_split_extent_at+0x121c/0x1240 fs/ext4/extents.c:3180
Code: fe c1 38 c1 0f 8c 16 fa ff ff e8 cf b7 cf ff 48 8b 54 24 58 48 8b 74 24 40 e9 02 fa ff ff e8 1b 18 92 ff 0f 0b e8 14 18 92 ff <0f> 0b e8 0d 18 92 ff 0f 0b e8 66 4f d5 02 e8 01 18 92 ff 0f 0b e8
RSP: 0018:ffffc90000b57820 EFLAGS: 00010293
RAX: ffffffff81d8a73c RBX: 0000000000000000 RCX: ffff88810d0e13c0
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000000000000000
RBP: ffffc90000b57990 R08: ffffffff81d897a2 R09: ffffc90000b57920
R10: fffff5200016af25 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 1ffff110226b35ff R15: 0000000000000000
FS:  00007f43d63ae6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000020000 CR3: 000000010b9fc000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/02 00:26 android13-5.10-lts 094fc3778d6b b8645499 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2 (corrupt fs)] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2025/02/12 08:04 android13-5.10-lts 6686f2996d23 f2baddf5 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2023/06/09 00:04 android13-5.10-lts 43c801dc3325 058b3a5a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2025/06/22 17:06 android13-5.10-lts d76d4cd0623a d6cdfb8a .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2025/02/27 03:27 android13-5.10-lts 3f5f2283d684 6a8fcbc4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2025/02/12 06:47 android13-5.10-lts 6686f2996d23 f2baddf5 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2022/12/14 02:28 android12-5.10-lts 202ee063496e f6511626 .config strace log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2025/05/29 13:35 android13-5.10-lts cf6ed0f1511d 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2023/06/08 22:36 android13-5.10-lts 43c801dc3325 058b3a5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 kernel BUG in ext4_split_extent_at
2022/11/08 00:29 android12-5.10-lts 0118fb827bc7 6feb842b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 kernel BUG in ext4_split_extent_at
* Struck through repros no longer work on HEAD.