syzbot

============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
kworker/u4:2/33 is trying to acquire lock:
ffff88801ee560b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28

but task is already holding lock:
ffff88801ee560b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 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/u4:2/33:
 #0: ffff888144a6a938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #1: ffffc90000a9fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #2: ffff888075842988 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x8d/0x220 fs/hfsplus/extents.c:149
 #3: ffff88801ee560b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
 #4: ffff888075840108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1cd/0x1a50 fs/hfsplus/extents.c:455

stack backtrace:
CPU: 0 PID: 33 Comm: kworker/u4:2 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 __lock_acquire+0x123e/0x7d10 kernel/locking/lockdep.c:-1
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747
 hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_file_extend+0x46a/0x1a50 fs/hfsplus/extents.c:459
 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x28d/0x5b0 fs/hfsplus/extents.c:104
 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline]
 hfsplus_ext_write_extent+0x194/0x220 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x1e/0x5b0 fs/hfsplus/super.c:167
 write_inode fs/fs-writeback.c:1470 [inline]
 __writeback_single_inode+0x75b/0x1160 fs/fs-writeback.c:1687
 writeback_sb_inodes+0xb30/0x1850 fs/fs-writeback.c:1913
 wb_writeback+0x482/0xd50 fs/fs-writeback.c:2087
 wb_do_writeback fs/fs-writeback.c:2230 [inline]
 wb_workfn+0x423/0xee0 fs/fs-writeback.c:2270
 process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
 worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>