[syzbot] [hfs?] WARNING: ODEBUG bug in hfsplus_fill_super (3)

[syzbot <syzbot+dd02382b022192737ea3@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    68b59730459e Merge tag 'perf-tools-for-v6.11-2024-07-16' o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d065e9980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b6230d83d52af231
dashboard link: https://syzkaller.appspot.com/bug?extid=dd02382b022192737ea3
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8229997a3dbb/disk-68b59730.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fd51823e0836/vmlinux-68b59730.xz
kernel image: https://storage.googleapis.com/syzbot-assets/01811b27f987/bzImage-68b59730.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dd02382b022192737ea3@syzkaller.appspotmail.com

hfsplus: b-tree write err: -5, ino 8
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88807bf16a38 object type: timer_list hint: delayed_sync_fs+0x0/0xf0
WARNING: CPU: 0 PID: 21527 at lib/debugobjects.c:518 debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515
Modules linked in:
CPU: 0 PID: 21527 Comm: syz.2.2751 Not tainted 6.10.0-syzkaller-08280-g68b59730459e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:debug_print_object+0x17a/0x1f0 lib/debugobjects.c:515
Code: e8 eb 1b 44 fd 4c 8b 0b 48 c7 c7 e0 64 20 8c 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 db fc 9f fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 1c 78 f6 0a 48 83 c4 10 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc900038275b8 EFLAGS: 00010286
RAX: 07a674bbf3926400 RBX: ffffffff8bccb7a0 RCX: 0000000000040000
RDX: ffffc9000e1eb000 RSI: 000000000002ed85 RDI: 000000000002ed86
RBP: ffffffff8c206660 R08: ffffffff81588142 R09: fffffbfff1c39da0
R10: dffffc0000000000 R11: fffffbfff1c39da0 R12: 0000000000000000
R13: ffffffff8c206578 R14: dffffc0000000000 R15: ffff88807bf16a38
FS:  00007f99cdb5a6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007eff0195d430 CR3: 000000005761c000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
 debug_check_no_obj_freed+0x45b/0x580 lib/debugobjects.c:1020
 slab_free_hook mm/slub.c:2163 [inline]
 slab_free mm/slub.c:4438 [inline]
 kfree+0x10f/0x360 mm/slub.c:4559
 hfsplus_fill_super+0xf25/0x1ca0 fs/hfsplus/super.c:618
 mount_bdev+0x20c/0x2d0 fs/super.c:1668
 legacy_get_tree+0xf0/0x190 fs/fs_context.c:662
 vfs_get_tree+0x92/0x2a0 fs/super.c:1789
 do_new_mount+0x2be/0xb40 fs/namespace.c:3472
 do_mount fs/namespace.c:3812 [inline]
 __do_sys_mount fs/namespace.c:4020 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f99ccd7725a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 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:00007f99cdb59e78 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f99cdb59f00 RCX: 00007f99ccd7725a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f99cdb59ec0
RBP: 0000000020000000 R08: 00007f99cdb59f00 R09: 0000000002000010
R10: 0000000002000010 R11: 0000000000000206 R12: 0000000020000100
R13: 00007f99cdb59ec0 R14: 00000000000006b5 R15: 0000000020000140
 </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 syzkaller@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