[Android 5.4] kernel panic: EXT4-fs (device loop0): panic forced after error
7 views
Skip to first unread message
syzbot
Aug 13, 2023, 5:27:52 AM8/13/23
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: fed9191809bc UPSTREAM: mm: memcontrol: set the correct mem..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16678553a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5e9b22184c611d9
dashboard link: https://syzkaller.appspot.com/bug?extid=e6249f3007a668343b13
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e35a65a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10febc65a80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3af9dc3441dc/disk-fed91918.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1c02bdd32937/vmlinux-fed91918.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b295dc08df26/bzImage-fed91918.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/59bf03734e2e/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e6249f...@syzkaller.appspotmail.com
EXT4-fs warning (device loop0): ext4_update_dynamic_rev:864: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs error (device loop0): ext4_validate_block_bitmap:409: comm syz-executor242: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 0 PID: 375 Comm: syz-executor242 Not tainted 5.4.249-syzkaller-00009-gfed9191809bc #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+0x1d8/0x241 lib/dump_stack.c:118
panic+0x309/0x896 kernel/panic.c:285
ext4_handle_error+0x3c2/0x3d0 fs/ext4/super.c:486
__ext4_error+0x1f9/0x490 fs/ext4/super.c:515
ext4_validate_block_bitmap+0xa8c/0xcd0 fs/ext4/balloc.c:408
ext4_read_block_bitmap+0x3a/0x80 fs/ext4/balloc.c:563
ext4_free_blocks+0x960/0x2310 fs/ext4/mballoc.c:4869
ext4_remove_blocks fs/ext4/extents.c:2726 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2879 [inline]
ext4_ext_remove_space+0x2758/0x4ba0 fs/ext4/extents.c:3124
ext4_truncate+0xb23/0x1290 fs/ext4/inode.c:4651
ext4_orphan_cleanup+0x8bc/0xd40 fs/ext4/super.c:2808
ext4_fill_super+0x8576/0x8d70 fs/ext4/super.c:4715
mount_bdev+0x267/0x370 fs/super.c:1417
legacy_get_tree+0xdf/0x170 fs/fs_context.c:647
vfs_get_tree+0x85/0x260 fs/super.c:1547
do_new_mount+0x292/0x570 fs/namespace.c:2843
do_mount+0x688/0xe10 fs/namespace.c:3163
ksys_mount+0xc2/0xf0 fs/namespace.c:3372
__do_sys_mount fs/namespace.c:3386 [inline]
__se_sys_mount fs/namespace.c:3383 [inline]
__x64_sys_mount+0xb1/0xc0 fs/namespace.c:3383
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: fed9191809bc UPSTREAM: mm: memcontrol: set the correct mem..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16678553a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5e9b22184c611d9
dashboard link: https://syzkaller.appspot.com/bug?extid=e6249f3007a668343b13
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e35a65a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10febc65a80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3af9dc3441dc/disk-fed91918.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1c02bdd32937/vmlinux-fed91918.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b295dc08df26/bzImage-fed91918.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/59bf03734e2e/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e6249f...@syzkaller.appspotmail.com
EXT4-fs warning (device loop0): ext4_update_dynamic_rev:864: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs error (device loop0): ext4_validate_block_bitmap:409: comm syz-executor242: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 0 PID: 375 Comm: syz-executor242 Not tainted 5.4.249-syzkaller-00009-gfed9191809bc #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+0x1d8/0x241 lib/dump_stack.c:118
panic+0x309/0x896 kernel/panic.c:285
ext4_handle_error+0x3c2/0x3d0 fs/ext4/super.c:486
__ext4_error+0x1f9/0x490 fs/ext4/super.c:515
ext4_validate_block_bitmap+0xa8c/0xcd0 fs/ext4/balloc.c:408
ext4_read_block_bitmap+0x3a/0x80 fs/ext4/balloc.c:563
ext4_free_blocks+0x960/0x2310 fs/ext4/mballoc.c:4869
ext4_remove_blocks fs/ext4/extents.c:2726 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2879 [inline]
ext4_ext_remove_space+0x2758/0x4ba0 fs/ext4/extents.c:3124
ext4_truncate+0xb23/0x1290 fs/ext4/inode.c:4651
ext4_orphan_cleanup+0x8bc/0xd40 fs/ext4/super.c:2808
ext4_fill_super+0x8576/0x8d70 fs/ext4/super.c:4715
mount_bdev+0x267/0x370 fs/super.c:1417
legacy_get_tree+0xdf/0x170 fs/fs_context.c:647
vfs_get_tree+0x85/0x260 fs/super.c:1547
do_new_mount+0x292/0x570 fs/namespace.c:2843
do_mount+0x688/0xe10 fs/namespace.c:3163
ksys_mount+0xc2/0xf0 fs/namespace.c:3372
__do_sys_mount fs/namespace.c:3386 [inline]
__se_sys_mount fs/namespace.c:3383 [inline]
__x64_sys_mount+0xb1/0xc0 fs/namespace.c:3383
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Aug 18, 2023, 12:47:03 PM8/18/23
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c2611a04b92f ANDROID: GKI: update symbol list file for xia..
syzbot found the following issue on:
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13ff9763a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5b8b7a65c87c651
dashboard link: https://syzkaller.appspot.com/bug?extid=73216f240bb65f795dd5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c0124ba80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1570dba0680000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/61093a06c07e/disk-c2611a04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4178a231c0bf/vmlinux-c2611a04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca97438b22a6/bzImage-c2611a04.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5eae50de9ae2/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
loop0: detected capacity change from 0 to 512
ext2: Unknown parameter '����'
EXT4-fs (loop0): feature flags set on rev 0 fs, running e2fsck is recommended
EXT4-fs (loop0): warning: checktime reached, running e2fsck is recommended
EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1084: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs error (device loop0): ext4_validate_block_bitmap:399: comm syz-executor238: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 0 PID: 317 Comm: syz-executor238 Not tainted 6.1.25-syzkaller-00052-gc2611a04b92f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
panic+0x283/0x660 kernel/panic.c:339
ext4_handle_error+0x83e/0x890 fs/ext4/super.c:687
__ext4_error+0x260/0x480 fs/ext4/super.c:778
ext4_validate_block_bitmap+0xd2f/0x1070 fs/ext4/balloc.c:398
ext4_wait_block_bitmap+0x144/0x1d0 fs/ext4/balloc.c:541
ext4_read_block_bitmap+0x41/0x80 fs/ext4/balloc.c:553
ext4_mb_clear_bb fs/ext4/mballoc.c:5935 [inline]
ext4_free_blocks+0x1009/0x2c10 fs/ext4/mballoc.c:6179
ext4_remove_blocks fs/ext4/extents.c:2545 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2711 [inline]
ext4_ext_remove_space+0x248b/0x4f50 fs/ext4/extents.c:2959
ext4_ext_truncate+0x1f4/0x320 fs/ext4/extents.c:4417
ext4_truncate+0x96c/0xfb0 fs/ext4/inode.c:4274
ext4_process_orphan+0x1d3/0x2f0 fs/ext4/orphan.c:339
ext4_orphan_cleanup+0xa4a/0x11e0 fs/ext4/orphan.c:474
__ext4_fill_super fs/ext4/super.c:5516 [inline]
ext4_fill_super+0x7d37/0x8450 fs/ext4/super.c:5644
get_tree_bdev+0x440/0x680 fs/super.c:1348
ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5674
vfs_get_tree+0x88/0x290 fs/super.c:1555
do_new_mount+0x28b/0xac0 fs/namespace.c:3040
path_mount+0x671/0x1070 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3568
__x64_sys_mount+0xbf/0xd0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4d87926a99
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:00007ffd7a8b7098 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f4d87926a99
RDX: 00000000200001c0 RSI: 00000000200006c0 RDI: 0000000020000640
RBP: 000000000000602d R08: 0000000000000000 R09: 0000555556b7c4c0
R10: 000000003f000000 R11: 0000000000000246 R12: 00007ffd7a8b70c0
R13: 00007ffd7a8b70ac R14: 431bde82d7b634db R15: 00007f4d8796f03b
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite bug's subsystems, reply with:
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages