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

Status: premoderation: reported syz repro on 2025/04/17 11:16
Reported-by: syzbot+4283c9f56fa6f545644a@syzkaller.appspotmail.com
First crash: 488d, last: 185d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/08/14 08:10 15m retest repro android13-5.10-lts report job log log
2026/08/14 08:10 8m retest repro android13-5.10-lts report job log log
2026/05/25 15:26 13m retest repro android13-5.10-lts log
2026/05/16 14:18 13m retest repro android13-5.10-lts log
2026/02/14 08:10 6m retest repro android13-5.10-lts report log
2025/12/06 07:50 7m retest repro android13-5.10-lts report log
2025/11/20 07:27 17m retest repro android13-5.10-lts report log
2025/09/27 00:42 10m retest repro android13-5.10-lts report log
2025/09/10 19:06 11m retest repro android13-5.10-lts report log
2025/07/16 00:25 8m retest repro android13-5.10-lts report log
▶ ▼ Fix bisection attempts (3)
Created Duration User Patch Repo Result
2026/03/16 09:24 4m bisect fix android13-5.10-lts error job log
2026/01/22 01:49 1h06m bisect fix android13-5.10-lts OK (0) job log log
2025/07/01 19:56 3h03m bisect fix android13-5.10-lts OK (0) job log log

Sample crash report:
EXT4-fs error (device loop1): ext4_get_branch:178: inode #13: block 2: comm syz.1.17: invalid block
Kernel panic - not syncing: EXT4-fs (device loop1): panic forced after error
CPU: 1 PID: 424 Comm: syz.1.17 Not tainted 5.10.236-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
 dump_stack+0x15/0x17 lib/dump_stack.c:135
 panic+0x2cf/0x812 kernel/panic.c:308
 ext4_handle_error+0x30e/0x310 fs/ext4/super.c:673
 __ext4_error_inode+0x2d8/0x5b0 fs/ext4/super.c:735
 ext4_check_blockref+0x22b/0x270 fs/ext4/block_validity.c:366
 ext4_get_branch+0x3d2/0x750 fs/ext4/indirect.c:178
 ext4_ind_map_blocks+0x586/0x2ab0 fs/ext4/indirect.c:552
 ext4_map_blocks+0x3f0/0x1d10 fs/ext4/inode.c:602
 _ext4_get_block+0x21b/0x610 fs/ext4/inode.c:816
 ext4_get_block fs/ext4/inode.c:833 [inline]
 __ext4_block_zero_page_range fs/ext4/inode.c:3866 [inline]
 ext4_block_zero_page_range+0x37d/0xa20 fs/ext4/inode.c:3944
 ext4_block_truncate_page fs/ext4/inode.c:3968 [inline]
 ext4_truncate+0xa4f/0x1220 fs/ext4/inode.c:4346
 ext4_orphan_cleanup+0x8e4/0xd50 fs/ext4/super.c:3100
 ext4_fill_super+0x888c/0x9150 fs/ext4/super.c:5075
 mount_bdev+0x262/0x370 fs/super.c:1442
 ext4_mount+0x34/0x40 fs/ext4/super.c:6645
 legacy_get_tree+0xf1/0x190 fs/fs_context.c:593
 vfs_get_tree+0x88/0x290 fs/super.c:1572
 do_new_mount+0x2ba/0xb30 fs/namespace.c:2917
 path_mount+0x56f/0xcb0 fs/namespace.c:3247
 do_mount fs/namespace.c:3260 [inline]
 __do_sys_mount fs/namespace.c:3468 [inline]
 __se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3445
 __x64_sys_mount+0xbf/0xd0 fs/namespace.c:3445
 do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f2ac4109169
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:00007f2ac3b7a038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f2ac4330fa0 RCX: 00007f2ac4109169
RDX: 00002000000001c0 RSI: 0000200000000240 RDI: 0000200000000000
RBP: 00007f2ac418ba68 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2ac4330fa0 R15: 00007fffbf7ec748
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/17 12:05 android13-5.10-lts ba8b8b193394 229db4cf .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 kernel panic: EXT4-fs (device loop1): panic forced after error
2025/04/17 11:15 android13-5.10-lts ba8b8b193394 229db4cf .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 kernel panic: EXT4-fs (device loop1): panic forced after error
* Struck through repros no longer work on HEAD.