[v6.6] WARNING in hfsplus_free_extents

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1655c034580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=eeffe9bd4b7829f1af23
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6383 at fs/hfsplus/extents.c:346 hfsplus_free_extents+0x6e9/0xac0 fs/hfsplus/extents.c:346
Modules linked in:
CPU: 0 PID: 6383 Comm: syz.3.109 Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:hfsplus_free_extents+0x6e9/0xac0 fs/hfsplus/extents.c:346
Code: 8b 1b 0f cb 89 ef 89 de e8 a4 62 32 ff 39 dd 75 20 49 83 c7 28 e8 17 61 32 ff 41 bc 05 00 00 00 e9 fa f9 ff ff e8 07 61 32 ff <0f> 0b e9 9d f9 ff ff 89 ef 89 de e8 77 62 32 ff 29 dd 73 0a e8 ee
RSP: 0018:ffffc90003f97910 EFLAGS: 00010287
RAX: ffffffff82533479 RBX: ffff88807be30020 RCX: 0000000000080000
RDX: ffffc9000d44d000 RSI: 000000000002ea41 RDI: 000000000002ea42
RBP: 000000000000001f R08: ffff88802380e04f R09: 1ffff11004701c09
R10: dffffc0000000000 R11: ffffed1004701c0a R12: ffff888023772000
R13: 00000000000000a8 R14: 0000000000000003 R15: ffff88802b56d158
FS: 00007fbe86da16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000039000 CR3: 000000003142b000 CR4: 00000000003506f0
Call Trace:
<TASK>
hfsplus_file_truncate+0x4e5/0xb40 fs/hfsplus/extents.c:608
hfsplus_write_begin+0xcc/0xd0 fs/hfsplus/inode.c:56
generic_perform_write+0x2fb/0x5b0 mm/filemap.c:4016
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4137
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fbe85f8e9a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbe86da1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fbe861b6080 RCX: 00007fbe85f8e9a9
RDX: 0000000000032600 RSI: 0000200000000000 RDI: 0000000000000004
RBP: 00007fbe86010d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fbe861b6080 R15: 00007ffd39e24578
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.