wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
hfsplus: b-tree write err: -5, ino 8
============================================
WARNING: possible recursive locking detected
6.7.0-rc8-syzkaller-00101-g0802e17d9aca #0 Not tainted
--------------------------------------------
kworker/u4:2/40 is trying to acquire lock:
ffff0000d985e0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc

but task is already holding lock:
ffff0000d985e0b0 (&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 kworker/u4:2/40:
 #0: ffff0000c1c3a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x560/0x1204 kernel/workqueue.c:2600
 #1: ffff8000943e7c20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x5a0/0x1204 kernel/workqueue.c:2602
 #2: ffff0000d9b78108 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x8c/0x1d8 fs/hfsplus/extents.c:149
 #3: ffff0000d985e0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc
 #4: ffff0000ce970108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:457

stack backtrace:
CPU: 0 PID: 40 Comm: kworker/u4:2 Not tainted 6.7.0-rc8-syzkaller-00101-g0802e17d9aca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: writeback wb_workfn (flush-7:0)
Call trace:
 dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106
 dump_stack+0x1c/0x28 lib/dump_stack.c:113
 print_deadlock_bug+0x4e4/0x660 kernel/locking/lockdep.c:3012
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x5fe4/0x763c kernel/locking/lockdep.c:5137
 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5754
 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799
 hfsplus_find_init+0x144/0x1bc
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_file_extend+0x370/0x1544 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_write_extent_locked fs/hfsplus/extents.c:139 [inline]
 hfsplus_ext_write_extent+0x158/0x1d8 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x34/0x4dc fs/hfsplus/super.c:154
 write_inode fs/fs-writeback.c:1473 [inline]
 __writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1690
 writeback_sb_inodes+0x718/0x1010 fs/fs-writeback.c:1916
 wb_writeback+0x3f4/0xfc0 fs/fs-writeback.c:2092
 wb_do_writeback fs/fs-writeback.c:2239 [inline]
 wb_workfn+0x37c/0xf9c fs/fs-writeback.c:2279
 process_one_work+0x694/0x1204 kernel/workqueue.c:2627
 process_scheduled_works kernel/workqueue.c:2700 [inline]
 worker_thread+0x938/0xef4 kernel/workqueue.c:2781
 kthread+0x288/0x310 kernel/kthread.c:388
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857