syzbot


kernel panic: EXT4-fs (device loop2): panic forced after error

Status: upstream: reported C repro on 2025/08/10 16:08
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+1ef6a6369301075a1f90@syzkaller.appspotmail.com
First crash: 9d19h, last: 9d19h
Bug presence (2)
Date Name Commit Repro Result
2025/08/11 lts (merge base) f2198ea7eb3e C [report] kernel panic: EXT4-fs (device loop2): panic forced after error
2025/08/11 upstream (ToT) 8f5ae30d69d7 C Didn't crash
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 kernel panic: EXT4-fs (device loop2): panic forced after error 2 1 738d 738d 0/2 auto-obsoleted due to no activity on 2023/11/10 21:00

Sample crash report:
loop2: detected capacity change from 0 to 512
ext4: Bad value for 'init_itable'
EXT4-fs error (device loop2): ext4_get_branch:178: inode #13: block 2: comm syz.2.17: invalid block
Kernel panic - not syncing: EXT4-fs (device loop2): panic forced after error
CPU: 1 PID: 374 Comm: syz.2.17 Not tainted 6.1.145-syzkaller-00002-gc750dc582629 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 __dump_stack+0x21/0x24 lib/dump_stack.c:88
 dump_stack_lvl+0xee/0x150 lib/dump_stack.c:106
 dump_stack+0x15/0x24 lib/dump_stack.c:113
 panic+0x283/0x698 kernel/panic.c:339
 ext4_handle_error+0x7a3/0x860 fs/ext4/super.c:687
 __ext4_error_inode+0x2ce/0x560 fs/ext4/super.c:811
 ext4_check_blockref+0x1c6/0x1d0 fs/ext4/block_validity.c:363
 ext4_get_branch+0x424/0x7c0 fs/ext4/indirect.c:178
 ext4_ind_map_blocks+0x255/0x1f30 fs/ext4/indirect.c:554
 ext4_map_blocks+0x373/0x1b60 fs/ext4/inode.c:608
 _ext4_get_block+0x1da/0x4e0 fs/ext4/inode.c:822
 ext4_get_block fs/ext4/inode.c:839 [inline]
 __ext4_block_zero_page_range fs/ext4/inode.c:3790 [inline]
 ext4_block_zero_page_range+0x396/0x9e0 fs/ext4/inode.c:3870
 ext4_block_truncate_page fs/ext4/inode.c:3894 [inline]
 ext4_truncate+0x8c3/0xf90 fs/ext4/inode.c:4271
 ext4_process_orphan+0x1d9/0x320 fs/ext4/orphan.c:339
 ext4_orphan_cleanup+0xb02/0x1210 fs/ext4/orphan.c:474
 __ext4_fill_super fs/ext4/super.c:5522 [inline]
 ext4_fill_super+0x73e6/0x7930 fs/ext4/super.c:5653
 get_tree_bdev+0x444/0x680 fs/super.c:1368
 ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5683
 vfs_get_tree+0x9a/0x270 fs/super.c:1575
 do_new_mount+0x25a/0xa20 fs/namespace.c:3058
 path_mount+0x675/0x1010 fs/namespace.c:3388
 do_mount fs/namespace.c:3401 [inline]
 __do_sys_mount fs/namespace.c:3609 [inline]
 __se_sys_mount+0x318/0x380 fs/namespace.c:3586
 __x64_sys_mount+0xbf/0xd0 fs/namespace.c:3586
 x64_sys_call+0x65d/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:166
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7485b8ebe9
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:00007f7486a43038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f7485db5fa0 RCX: 00007f7485b8ebe9
RDX: 00002000000001c0 RSI: 0000200000000240 RDI: 0000200000000000
RBP: 00007f7485c11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7485db6038 R14: 00007f7485db5fa0 R15: 00007ffeac062d28
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/10 16:08 android14-6.1 c750dc582629 32a0e5ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-6-1 kernel panic: EXT4-fs (device loop2): panic forced after error
* Struck through repros no longer work on HEAD.