IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
kworker/u4:3/155 is trying to acquire lock:
ffff888022d4c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28

but task is already holding lock:
ffff888022d4c0b0 (&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:3/155:
 #0: ffff8880191a0138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc90002047d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffff88802352a988 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x8d/0x230 fs/hfsplus/extents.c:149
 #3: ffff888022d4c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
 #4: ffff888023528108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1ca/0x1a40 fs/hfsplus/extents.c:455

stack backtrace:
CPU: 0 PID: 155 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 __lock_acquire+0x1247/0x7b50 kernel/locking/lockdep.c:-1
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_file_extend+0x465/0x1a40 fs/hfsplus/extents.c:459
 hfsplus_bmap_reserve+0x107/0x510 fs/hfsplus/btree.c:357
 __hfsplus_ext_write_extent+0x264/0x520 fs/hfsplus/extents.c:104
 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline]
 hfsplus_ext_write_extent+0x197/0x230 fs/hfsplus/extents.c:150
 hfsplus_write_inode+0x1e/0x570 fs/hfsplus/super.c:173
 write_inode fs/fs-writeback.c:1505 [inline]
 __writeback_single_inode+0x6c4/0xda0 fs/fs-writeback.c:1715
 writeback_sb_inodes+0xaaa/0x1750 fs/fs-writeback.c:1940
 wb_writeback+0x44a/0xbc0 fs/fs-writeback.c:2114
 wb_do_writeback fs/fs-writeback.c:2257 [inline]
 wb_workfn+0x43a/0xf20 fs/fs-writeback.c:2298
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>