wlan0: Creating new IBSS network, BSSID 50:50:50:50:50:50
============================================
WARNING: possible recursive locking detected
6.10.0-syzkaller-12888-g5437f30d3458 #0 Not tainted
--------------------------------------------
kworker/u8:9/3710 is trying to acquire lock:
ffff88802be780b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x17b/0x1f0 fs/hfsplus/bfind.c:28

but task is already holding lock:
ffff88802be780b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x17b/0x1f0 fs/hfsplus/bfind.c:28

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/u8:9/3710:
 #0: ffff888018efb148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x1277/0x1b40 kernel/workqueue.c:3206
 #1: ffffc9000a757d80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x921/0x1b40 kernel/workqueue.c:3207
 #2: ffff888075dea988 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x82/0x210 fs/hfsplus/extents.c:149
 #3: ffff88802be780b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x17b/0x1f0 fs/hfsplus/bfind.c:28
 #4: ffff888075de8108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:458

stack backtrace:
CPU: 1 UID: 0 PID: 3710 Comm: kworker/u8:9 Not tainted 6.10.0-syzkaller-12888-g5437f30d3458 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119
 check_deadlock kernel/locking/lockdep.c:3061 [inline]
 validate_chain kernel/locking/lockdep.c:3855 [inline]
 __lock_acquire+0x2167/0x3cb0 kernel/locking/lockdep.c:5142
 lock_acquire kernel/locking/lockdep.c:5759 [inline]
 lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5724
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
 hfsplus_find_init+0x17b/0x1f0 fs/hfsplus/bfind.c:28
 hfsplus_ext_read_extent+0x18f/0x250 fs/hfsplus/extents.c:216
 hfsplus_file_extend+0x699/0x1090 fs/hfsplus/extents.c:462
 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x474/0x5e0 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+0x1c9/0x210 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x22/0x4f0 fs/hfsplus/super.c:154
 write_inode fs/fs-writeback.c:1497 [inline]
 __writeback_single_inode+0xb39/0xf90 fs/fs-writeback.c:1716
 writeback_sb_inodes+0x611/0x1150 fs/fs-writeback.c:1947
 wb_writeback+0x199/0xb50 fs/fs-writeback.c:2127
 wb_do_writeback fs/fs-writeback.c:2274 [inline]
 wb_workfn+0x28d/0xf40 fs/fs-writeback.c:2314
 process_one_work+0x9c8/0x1b40 kernel/workqueue.c:3231
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf20 kernel/workqueue.c:3390
 kthread+0x2c4/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>