hfsplus: walked past end of dir
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.32/6128 is trying to acquire lock:
ffff8880400480f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1fc/0x19a0 fs/hfsplus/extents.c:455

but task is already holding lock:
ffff888062bf1ef8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_ext_write_extent+0x8a/0x200 fs/hfsplus/extents.c:149

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&HFSPLUS_I(inode)->extents_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by syz.0.32/6128:
 #0: ffff888041bf4488 (sb_writers#21){.+.+}-{0:0}, at: direct_splice_actor+0x49/0x160 fs/splice.c:1160
 #1: ffff888062bf2158 (&sb->s_type->i_mutex_key#27){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:870 [inline]
 #1: ffff888062bf2158 (&sb->s_type->i_mutex_key#27){+.+.}-{4:4}, at: hfsplus_file_fsync+0xf8/0x510 fs/hfsplus/inode.c:313
 #2: ffff888062bf1ef8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_ext_write_extent+0x8a/0x200 fs/hfsplus/extents.c:149
 #3: ffff88803d4460a0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfsplus_find_init+0x15a/0x1d0 fs/hfsplus/bfind.c:28

stack backtrace:
CPU: 0 UID: 0 PID: 6128 Comm: syz.0.32 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3895
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
 hfsplus_file_extend+0x1fc/0x19a0 fs/hfsplus/extents.c:455
 hfsplus_bmap_reserve+0x125/0x500 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x2b0/0x5e0 fs/hfsplus/extents.c:104
 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline]
 hfsplus_ext_write_extent+0x17a/0x200 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x22/0x5f0 fs/hfsplus/super.c:155
 write_inode fs/fs-writeback.c:1525 [inline]
 __writeback_single_inode+0x6f4/0x1000 fs/fs-writeback.c:1745
 writeback_single_inode+0x1d5/0x640 fs/fs-writeback.c:1801
 sync_inode_metadata+0xb9/0x110 fs/fs-writeback.c:2884
 hfsplus_file_fsync+0x105/0x510 fs/hfsplus/inode.c:318
 generic_write_sync include/linux/fs.h:3043 [inline]
 generic_file_write_iter+0x31c/0x550 mm/filemap.c:4322
 iter_file_splice_write+0x97a/0x10f0 fs/splice.c:738
 do_splice_from fs/splice.c:938 [inline]
 direct_splice_actor+0x104/0x160 fs/splice.c:1161
 splice_direct_to_actor+0x5b3/0xcd0 fs/splice.c:1105
 do_splice_direct_actor fs/splice.c:1204 [inline]
 do_splice_direct+0x187/0x270 fs/splice.c:1230
 do_sendfile+0x4ec/0x7f0 fs/read_write.c:1370
 __do_sys_sendfile64 fs/read_write.c:1431 [inline]
 __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd375f9ec29
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:00007fd3741fe038 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fd3761e5fa0 RCX: 00007fd375f9ec29
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000004
RBP: 00007fd376021e41 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020fffe82 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd3761e6038 R14: 00007fd3761e5fa0 R15: 00007ffc87aff488
 </TASK>