syzbot


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

Status: closed as invalid on 2022/12/26 14:10
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+9a3867e6af15bf0d031c@syzkaller.appspotmail.com
First crash: 522d, last: 522d
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 522d 518d 0/26 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 30d 191d 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 2216d 2216d 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 291d 287d 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 9d11h 286d 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 85d 85d 0/3 upstream: reported C repro on 2024/03/06 01:35
android-54 kernel panic: EXT4-fs (device loop0): panic forced after error C 1 63d 291d 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 522d 522d 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 inconclusive 1 53d 291d 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 2216d 2216d 0/3 closed as invalid on 2018/05/07 15:46

Sample crash report:
EXT4-fs error (device loop0): ext4_map_blocks:594: inode #2: block 2: comm syz-executor283: lblock 0 mapped to illegal pblock 2 (length 1)
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 1 PID: 376 Comm: syz-executor283 Not tainted 5.10.160-syzkaller-01321-g003c389455eb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
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+0x2a0/0x7d7 kernel/panic.c:231
 ext4_handle_error+0x30e/0x310 fs/ext4/super.c:688
 __ext4_error_inode+0x2c7/0x580 fs/ext4/super.c:750
 ext4_map_blocks+0x1313/0x1ee0 fs/ext4/inode.c:410
 ext4_getblk+0x19c/0x650 fs/ext4/inode.c:849
 ext4_bread+0x2f/0x1b0 fs/ext4/inode.c:901
 __ext4_read_dirblock+0xa0/0x8e0 fs/ext4/namei.c:138
 dx_probe+0xcd/0x15a0 fs/ext4/namei.c:793
 ext4_dx_find_entry fs/ext4/namei.c:1758 [inline]
 __ext4_find_entry+0x5b9/0x1b90 fs/ext4/namei.c:1601
 ext4_lookup_entry fs/ext4/namei.c:1739 [inline]
 ext4_lookup+0x3e1/0xb20 fs/ext4/namei.c:1809
 __lookup_slow+0x2b3/0x400 fs/namei.c:1630
 lookup_slow fs/namei.c:1647 [inline]
 lookup_one_len_unlocked+0x458/0x680 fs/namei.c:2673
 lookup_positive_unlocked+0x25/0xb0 fs/namei.c:2689
 dquot_quota_on_mount+0x5a/0xe0 fs/quota/dquot.c:2507
 ext4_quota_on_mount fs/ext4/super.c:6276 [inline]
 ext4_orphan_cleanup+0x3f2/0xdb0 fs/ext4/super.c:3073
 ext4_fill_super+0x8880/0x9150 fs/ext4/super.c:5087
 mount_bdev+0x25f/0x370 fs/super.c:1420
 ext4_mount+0x34/0x40 fs/ext4/super.c:6606
 legacy_get_tree+0xf0/0x190 fs/fs_context.c:592
 vfs_get_tree+0x88/0x290 fs/super.c:1550
 do_new_mount+0x289/0xad0 fs/namespace.c:2899
 path_mount+0x58d/0xce0 fs/namespace.c:3229
 do_mount fs/namespace.c:3242 [inline]
 __do_sys_mount fs/namespace.c:3450 [inline]
 __se_sys_mount+0x2d2/0x3c0 fs/namespace.c:3427
 __x64_sys_mount+0xbf/0xd0 fs/namespace.c:3427
 do_syscall_64+0x34/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fef9239bbca
Code: 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffff0a3d988 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fef9239bbca
RDX: 0000000020000440 RSI: 0000000020000480 RDI: 00007ffff0a3d9a0
RBP: 00007ffff0a3d9a0 R08: 00007ffff0a3d9e0 R09: 0000000000000474
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000004
R13: 0000555555bfd2c0 R14: 0000000000000000 R15: 00007ffff0a3d9e0
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
2022/12/24 20:11 android12-5.10-lts 003c389455eb 9da18ae8 .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.