============================================
WARNING: possible recursive locking detected
6.4.0-rc2-next-20230515-syzkaller #0 Not tainted
--------------------------------------------
kworker/u4:0/10 is trying to acquire lock:
ffff888079bd20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x182/0x240 fs/hfs/bfind.c:33

but task is already holding lock:
ffff888079bd20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x182/0x240 fs/hfs/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

4 locks held by kworker/u4:0/10:
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888145a7d938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2378
 #1: ffffc900000f7db0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2382
 #2: ffff888079bd20b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x182/0x240 fs/hfs/bfind.c:33
 #3: ffff8880790400f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0x97/0xae0 fs/hfs/extent.c:397

stack backtrace:
CPU: 0 PID: 10 Comm: kworker/u4:0 Not tainted 6.4.0-rc2-next-20230515-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/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.part.0+0x11c/0x370 kernel/locking/lockdep.c:5705
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 hfs_find_init+0x182/0x240 fs/hfs/bfind.c:33
 hfs_ext_read_extent+0x18d/0xa20 fs/hfs/extent.c:200
 hfs_extend_file+0x4b5/0xae0 fs/hfs/extent.c:401
 hfs_bmap_reserve+0x29f/0x380 fs/hfs/btree.c:234
 __hfs_ext_write_extent+0x3c1/0x510 fs/hfs/extent.c:121
 hfs_ext_write_extent fs/hfs/extent.c:144 [inline]
 hfs_ext_write_extent+0x1a6/0x1f0 fs/hfs/extent.c:135
 hfs_write_inode+0x95/0x9d0 fs/hfs/inode.c:431
 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+0x155/0xa40 fs/fs-writeback.c:2070
 wb_do_writeback fs/fs-writeback.c:2217 [inline]
 wb_workfn+0x2a5/0xcc0 fs/fs-writeback.c:2257
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2407
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2554
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>