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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4a4be1ad3a6e Revert "vfs: Delete the associated dentry whe..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105f7dec980000
kernel config: https://syzkaller.appspot.com/x/.config?x=238430243a58f702
dashboard link: https://syzkaller.appspot.com/bug?extid=f4972c2c269fc92935f5
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b1ea85ab1f5b/disk-4a4be1ad.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/681d06438c4b/vmlinux-4a4be1ad.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f422d33e089/bzImage-4a4be1ad.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88805a0d3a38 object type: timer_list hint: delayed_sync_fs+0x0/0xf0 fs/hfsplus/super.c:300
WARNING: CPU: 1 PID: 6129 at lib/debugobjects.c:514 debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514
Modules linked in:
CPU: 1 PID: 6129 Comm: syz-executor.0 Not tainted 6.10.0-rc1-syzkaller-00027-g4a4be1ad3a6e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 48 8b 14 dd c0 11 90 8b 41 56 4c 89 e6 48 c7 c7 20 05 90 8b e8 6e 3e c6 fc 90 <0f> 0b 90 90 58 83 05 25 e1 5a 0b 01 48 83 c4 18 5b 5d 41 5c 41 5d
RSP: 0018:ffffc900041bf6a8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffc90009f74000
RDX: 0000000000040000 RSI: ffffffff814ff016 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff8b900bc0
R13: ffffffff8b2f28e0 R14: ffffffff8269cbd0 R15: ffffc900041bf7b8
FS: 00007f4e6ec756c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020030000 CR3: 000000001e906000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:989 [inline]
debug_check_no_obj_freed+0x4b8/0x600 lib/debugobjects.c:1019
slab_free_hook mm/slub.c:2162 [inline]
slab_free mm/slub.c:4436 [inline]
kfree+0x284/0x3b0 mm/slub.c:4557
hfsplus_fill_super+0xf44/0x1bc0 fs/hfsplus/super.c:618
mount_bdev+0x1e3/0x2d0 fs/super.c:1659
legacy_get_tree+0x109/0x220 fs/fs_context.c:662
vfs_get_tree+0x8f/0x380 fs/super.c:1780
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4e6de7e5ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4e6ec74ef8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f4e6ec74f80 RCX: 00007f4e6de7e5ea
RDX: 0000000020000000 RSI: 0000000020000080 RDI: 00007f4e6ec74f40
RBP: 0000000020000000 R08: 00007f4e6ec74f80 R09: 0000000002000010
R10: 0000000002000010 R11: 0000000000000206 R12: 0000000020000080
R13: 00007f4e6ec74f40 R14: 00000000000006a6 R15: 0000000020000100
</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