Hello,
syzbot found the following issue on:
HEAD commit: c596736dadab Linux 6.6.120
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10c8799a580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link:
https://syzkaller.appspot.com/bug?extid=3f50795f61cc35054f74
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/855c94eb3eef/disk-c596736d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/b7510b30b774/vmlinux-c596736d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3ce7fe4f6991/bzImage-c596736d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3f5079...@syzkaller.appspotmail.com
F2FS-fs (loop1): Failed to get valid F2FS checkpoint
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff888030f218f8 object type: work_struct hint: cur_cp_version fs/f2fs/f2fs.h:-1 [inline]
ODEBUG: free active (active state 0) object: ffff888030f218f8 object type: work_struct hint: f2fs_record_error_work+0x0/0x1d0 fs/f2fs/super.c:4725
WARNING: CPU: 0 PID: 6091 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 0 PID: 6091 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 0 PID: 6091 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 0 PID: 6091 Comm: syz.1.78 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:debug_print_object lib/debugobjects.c:515 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 60 7d fc 8a 48 c7 c6 c0 79 fc 8a 48 c7 c2 e0 7e fc 8a 8b 0c 24 4d 89 f8 41 55 e8 2e 73 29 fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 f3 d4 23
RSP: 0018:ffffc90004f5f910 EFLAGS: 00010292
RAX: a2594fc8c81a4500 RBX: ffffffff970f77d8 RCX: 0000000000080000
RDX: ffffc9000d44a000 RSI: 000000000002500d RDI: 000000000002500e
RBP: ffffffff8aa9ea40 R08: ffffc90004f5f507 R09: 1ffff920009ebea0
R10: dffffc0000000000 R11: fffff520009ebea1 R12: ffff888030f22000
R13: ffffffff83b10ba0 R14: ffff888030f21000 R15: ffff888030f218f8
FS: 00007f8319c1b6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8318d72a60 CR3: 00000000246c8000 CR4: 00000000003506f0
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1786 [inline]
slab_free_freelist_hook+0xd2/0x1b0 mm/slub.c:1837
slab_free mm/slub.c:3830 [inline]
__kmem_cache_free+0xba/0x1f0 mm/slub.c:3843
f2fs_fill_super+0x3dad/0x6cc0 fs/f2fs/super.c:4809
mount_bdev+0x22b/0x2d0 fs/super.c:1643
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
do_new_mount+0x24b/0xa40 fs/namespace.c:3386
do_mount fs/namespace.c:3726 [inline]
__do_sys_mount fs/namespace.c:3935 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3912
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8318d90eea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f8319c1ae68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f8319c1aef0 RCX: 00007f8318d90eea
RDX: 00002000000002c0 RSI: 0000200000000440 RDI: 00007f8319c1aeb0
RBP: 00002000000002c0 R08: 00007f8319c1aef0 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000246 R12: 0000200000000440
R13: 00007f8319c1aeb0 R14: 0000000000005512 R15: 0000200000000dc0
</TASK>
---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup