syzbot

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

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

Status: upstream: reported C repro on 2023/08/12 21:25
Reported-by: syzbot+e9caa43f4f89b426598a@syzkaller.appspotmail.com
First crash: 466d, last: 57d
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
▶ ▼ 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 697d 693d 0/28 closed as invalid on 2023/01/03 13:41
linux-6.1 kernel panic: EXT4-fs (device loop0): panic forced after error origin:upstream C 1 17d 366d 0/3 upstream: reported C repro on 2023/11/20 19:54
upstream kernel panic: EXT4-fs (device loop0): panic forced after error ext4 C 1 2391d 2391d 0/28 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 466d 462d 0/28 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 inconclusive 1 3d18h 461d 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 45d 260d 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 697d 697d 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 27d 466d 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 697d 697d 0/2 closed as invalid on 2022/12/26 14:01
android-49 kernel panic: EXT4-fs (device loop0): panic forced after error C 2 2391d 2391d 0/3 closed as invalid on 2018/05/07 15:46
▶ ▼ Last patch testing requests (3)
Created Duration User Patch Repo Result
2024/09/24 23:12 51m retest repro android13-5.10-lts report log
2024/07/16 21:54 5m retest repro android13-5.10-lts report log
2023/08/28 18:25 6m retest repro android13-5.10-lts report log
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2024/05/07 20:35 30m bisect fix android13-5.10-lts OK (0) job log
2024/04/06 19:05 55m bisect fix android13-5.10-lts OK (0) job log log
2024/03/06 22:09 46m bisect fix android13-5.10-lts OK (0) job log log
2024/02/02 07:36 34m bisect fix android13-5.10-lts OK (0) job log log
2023/12/30 06:22 33m bisect fix android13-5.10-lts OK (0) job log log
2023/11/30 04:39 37m bisect fix android13-5.10-lts OK (0) job log log
2023/10/29 19:45 59m bisect fix android13-5.10-lts OK (0) job log log
2023/09/28 18:21 48m bisect fix android13-5.10-lts OK (0) job log log

Sample crash report:
EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1047: 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-executor401: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 0 PID: 292 Comm: syz-executor401 Not tainted 5.10.187-syzkaller-00057-g8a427269c016 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
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/0x80b kernel/panic.c:308
 ext4_handle_error+0x30e/0x310 fs/ext4/super.c:673
 __ext4_error+0x203/0x420 fs/ext4/super.c:703
 ext4_validate_block_bitmap+0xe5b/0x1010
 ext4_wait_block_bitmap+0x1ac/0x1d0 fs/ext4/balloc.c:579
 ext4_read_block_bitmap+0x41/0x80 fs/ext4/balloc.c:591
 ext4_mb_clear_bb fs/ext4/mballoc.c:5473 [inline]
 ext4_free_blocks+0xdcb/0x27a0 fs/ext4/mballoc.c:5716
 ext4_remove_blocks fs/ext4/extents.c:2538 [inline]
 ext4_ext_rm_leaf fs/ext4/extents.c:2704 [inline]
 ext4_ext_remove_space+0x260f/0x4e10 fs/ext4/extents.c:2952
 ext4_ext_truncate+0x17f/0x200 fs/ext4/extents.c:4413
 ext4_truncate+0xb19/0x1220 fs/ext4/inode.c:4365
 ext4_orphan_cleanup+0x8e4/0xd50 fs/ext4/super.c:3100
 ext4_fill_super+0x89a5/0x9280 fs/ext4/super.c:5075
 mount_bdev+0x262/0x370 fs/super.c:1420
 ext4_mount+0x34/0x40 fs/ext4/super.c:6625
 legacy_get_tree+0xf1/0x190 fs/fs_context.c:592
 vfs_get_tree+0x88/0x290 fs/super.c:1550
 do_new_mount+0x28b/0xad0 fs/namespace.c:2899
 path_mount+0x56f/0xcb0 fs/namespace.c:3229
 do_mount fs/namespace.c:3242 [inline]
 __do_sys_mount fs/namespace.c:3450 [inline]
 __se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3427
 __x64_sys_mount+0xbf/0xd0 fs/namespace.c:3427
 do_syscall_64+0x34/0x70
 entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fe77597e1d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcdc0092f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe77597e1d9
RDX: 00000000200001c0 RSI: 00000000200006c0 RDI: 0000000020000640
RBP: 0000000000000000 R08: 0000000000000000 R09: 00007ffcdc009330
R10: 000000003f000000 R11: 0000000000000246 R12: 00007ffcdc009330
R13: 00007ffcdc0095b8 R14: 431bde82d7b634db R15: 00007fe7759c703b
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
2023/08/12 21:24 android13-5.10-lts 8a427269c016 39990d51 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-10 kernel panic: EXT4-fs (device loop0): panic forced after error
* Struck through repros no longer work on HEAD.