syzbot


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

Status: upstream: reported C repro on 2023/11/20 19:54
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+d940ca48e153ad86cb0f@syzkaller.appspotmail.com
First crash: 158d, last: 29d
Bug presence (1)
Date Name Commit Repro Result
2023/11/20 upstream (ToT) 98b1cc82c4af C [report] kernel panic: EXT4-fs (device loop0): panic forced after error
Similar bugs (10)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: EXT4-fs (device loop0): panic forced after error (2) ext4 C error 2 489d 485d 0/26 closed as invalid on 2023/01/03 13:41
upstream kernel panic: EXT4-fs (device loop0): panic forced after error ext4 C 1 2183d 2183d 0/26 closed as invalid on 2018/06/12 14:01
upstream kernel panic: EXT4-fs (device loop0): panic forced after error (3) ext4 C inconclusive 1 258d 254d 0/26 closed as invalid on 2023/08/17 14:21
android-6-1 kernel panic: EXT4-fs (device loop0): panic forced after error origin:upstream C error 1 11d 253d 0/2 upstream: reported C repro on 2023/08/18 16:47
linux-5.15 kernel panic: EXT4-fs (device loop0): panic forced after error origin:upstream C error 1 52d 52d 0/3 upstream: reported C repro on 2024/03/06 01:35
android-5-10 kernel panic: EXT4-fs (device loop0): panic forced after error ext4 C 1 489d 489d 0/2 closed as invalid on 2022/12/26 14:10
android-54 kernel panic: EXT4-fs (device loop0): panic forced after error C 1 30d 258d 0/2 upstream: reported C repro on 2023/08/13 09:27
android-5-15 kernel panic: EXT4-fs (device loop0): panic forced after error ext4 C error 1 489d 489d 0/2 closed as invalid on 2022/12/26 14:01
android-5-10 kernel panic: EXT4-fs (device loop0): panic forced after error (2) C 1 20d 258d 0/2 upstream: reported C repro on 2023/08/12 21:25
android-49 kernel panic: EXT4-fs (device loop0): panic forced after error C 2 2183d 2183d 0/3 closed as invalid on 2018/05/07 15:46
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2024/03/29 13:11 2h03m bisect fix linux-6.1.y job log (0) log
2024/02/28 07:10 1h57m bisect fix linux-6.1.y job log (0) log
2024/01/20 00:01 1h31m bisect fix linux-6.1.y job log (0) log
2023/12/20 19:58 2h00m bisect fix linux-6.1.y job log (0) log

Sample crash report:
EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1085: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs error (device loop0): ext4_validate_block_bitmap:429: comm syz-executor238: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 1 PID: 4221 Comm: syz-executor238 Not tainted 6.1.63-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 panic+0x300/0x7fc kernel/panic.c:339
 ext4_handle_error+0x750/0x798 fs/ext4/super.c:686
 __ext4_error+0x20c/0x2dc fs/ext4/super.c:777
 ext4_validate_block_bitmap+0xc6c/0xfd0
 ext4_wait_block_bitmap+0x18c/0x1cc fs/ext4/balloc.c:580
 ext4_read_block_bitmap+0x54/0xd4 fs/ext4/balloc.c:592
 ext4_mb_clear_bb fs/ext4/mballoc.c:5991 [inline]
 ext4_free_blocks+0xd3c/0x2b68 fs/ext4/mballoc.c:6236
 ext4_remove_blocks fs/ext4/extents.c:2545 [inline]
 ext4_ext_rm_leaf fs/ext4/extents.c:2711 [inline]
 ext4_ext_remove_space+0x1bd0/0x4544 fs/ext4/extents.c:2959
 ext4_ext_truncate+0x168/0x210 fs/ext4/extents.c:4417
 ext4_truncate+0xa08/0x1178 fs/ext4/inode.c:4265
 ext4_process_orphan+0x180/0x2b8 fs/ext4/orphan.c:339
 ext4_orphan_cleanup+0x974/0x1134 fs/ext4/orphan.c:474
 __ext4_fill_super fs/ext4/super.c:5533 [inline]
 ext4_fill_super+0x6f04/0x7570 fs/ext4/super.c:5664
 get_tree_bdev+0x360/0x54c fs/super.c:1355
 ext4_get_tree+0x28/0x38 fs/ext4/super.c:5694
 vfs_get_tree+0x90/0x274 fs/super.c:1562
 do_new_mount+0x25c/0x8c4 fs/namespace.c:3040
 path_mount+0x590/0xe5c fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x00000,02070084,26017203
Memory Limit: none
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/11/20 19:53 linux-6.1.y 69e434a1cb21 cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 kernel panic: EXT4-fs (device loop0): panic forced after error
* Struck through repros no longer work on HEAD.