============================================
WARNING: possible recursive locking detected
6.4.0-rc6-syzkaller-00006-gfd37b884003c #0 Not tainted
--------------------------------------------
kworker/u4:0/10 is trying to acquire lock:
ffff88807636c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x174/0x230 fs/hfsplus/bfind.c:33

but task is already holding lock:
ffff88807636c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x174/0x230 fs/hfsplus/bfind.c:33

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 kworker/u4:0/10:
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888144a6e938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc900000f7db0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
 #2: ffff88807e578108 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x82/0x200 fs/hfsplus/extents.c:149
 #3: ffff88807636c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x174/0x230 fs/hfsplus/bfind.c:33
 #4: ffff888075a50108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1bf/0xf90 fs/hfsplus/extents.c:457

stack backtrace:
CPU: 1 PID: 10 Comm: kworker/u4:0 Not tainted 6.4.0-rc6-syzkaller-00006-gfd37b884003c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:3006 [inline]
 check_deadlock kernel/locking/lockdep.c:3049 [inline]
 validate_chain kernel/locking/lockdep.c:3834 [inline]
 __lock_acquire+0x13eb/0x5f30 kernel/locking/lockdep.c:5088
 lock_acquire kernel/locking/lockdep.c:5705 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 hfsplus_find_init+0x174/0x230 fs/hfsplus/bfind.c:33
 hfsplus_ext_read_extent+0x185/0xae0 fs/hfsplus/extents.c:216
 hfsplus_file_extend+0x684/0xf90 fs/hfsplus/extents.c:461
 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x44b/0x5b0 fs/hfsplus/extents.c:104
 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline]
 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:129 [inline]
 hfsplus_ext_write_extent+0x1ba/0x200 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x22/0x520 fs/hfsplus/super.c:154
 write_inode fs/fs-writeback.c:1456 [inline]
 __writeback_single_inode+0x9f2/0xdb0 fs/fs-writeback.c:1668
 writeback_sb_inodes+0x54d/0xe70 fs/fs-writeback.c:1894
 wb_writeback+0x294/0xa50 fs/fs-writeback.c:2068
 wb_do_writeback fs/fs-writeback.c:2211 [inline]
 wb_workfn+0x2a5/0xfc0 fs/fs-writeback.c:2251
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>