loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
6.1.31-syzkaller #0 Not tainted
--------------------------------------------
syz-executor516/4215 is trying to acquire lock:
ffff0000d5cc20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc

but task is already holding lock:
ffff0000d5cc20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc

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

       CPU0
       ----
  lock(&tree->tree_lock/1);
  lock(&tree->tree_lock/1);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

5 locks held by syz-executor516/4215:
 #0: ffff0000d5cc0460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x244/0x914 fs/read_write.c:580
 #1: ffff0000de24a4c0 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #1: ffff0000de24a4c0 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: generic_file_write_iter+0x88/0x2b4 mm/filemap.c:3911
 #2: ffff0000de24a2c8 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x198/0x14cc fs/hfsplus/extents.c:457
 #3: ffff0000d5cc20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc
 #4: ffff0000de248108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x198/0x14cc fs/hfsplus/extents.c:457

stack backtrace:
CPU: 0 PID: 4215 Comm: syz-executor516 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 __lock_acquire+0x6310/0x764c kernel/locking/lockdep.c:5056
 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669
 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
 hfsplus_find_init+0x144/0x1bc
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_file_extend+0x364/0x14cc fs/hfsplus/extents.c:461
 hfsplus_bmap_reserve+0xec/0x474 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x1e8/0x4ac fs/hfsplus/extents.c:104
 __hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
 hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
 hfsplus_file_extend+0x390/0x14cc fs/hfsplus/extents.c:461
 hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245
 __block_write_begin_int+0x340/0x13b4 fs/buffer.c:1991
 __block_write_begin fs/buffer.c:2041 [inline]
 block_write_begin fs/buffer.c:2102 [inline]
 cont_write_begin+0x5c0/0x7d8 fs/buffer.c:2456
 hfsplus_write_begin+0x98/0xe4 fs/hfsplus/inode.c:52
 generic_perform_write+0x278/0x55c mm/filemap.c:3754
 __generic_file_write_iter+0x168/0x388 mm/filemap.c:3882
 generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:3914
 call_write_iter include/linux/fs.h:2205 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x610/0x914 fs/read_write.c:584
 ksys_write+0x15c/0x26c fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581