============================================
WARNING: possible recursive locking detected
6.14.0-rc3-syzkaller-ga1c24ab82279 #0 Not tainted
--------------------------------------------
syz.4.28/6708 is trying to acquire lock:
ffff0000d5cbd208 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:458

but task is already holding lock:
ffff0000d5cbdf88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:458

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&HFSPLUS_I(inode)->extents_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

6 locks held by syz.4.28/6708:
 #0: ffff0000c9e1a0e0 (&type->s_umount_key#52/1){+.+.}-{4:4}, at: alloc_super+0x1b0/0x834 fs/super.c:344
 #1: ffff0000f0795998 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_fill_super+0xf40/0x16f8 fs/hfsplus/super.c:554
 #2: ffff0000ca71a0b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x144/0x1bc fs/hfsplus/bfind.c:28
 #3: ffff0000ca0e60b0 (&tree->tree_lock/2){+.+.}-{4:4}, at: hfsplus_find_init+0x144/0x1bc fs/hfsplus/bfind.c:28
 #4: ffff0000d5cbdf88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:458
 #5: ffff0000ca71c0b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x144/0x1bc fs/hfsplus/bfind.c:28

stack backtrace:
CPU: 0 UID: 0 PID: 6708 Comm: syz.4.28 Not tainted 6.14.0-rc3-syzkaller-ga1c24ab82279 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C)
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_deadlock_bug+0x4e8/0x668 kernel/locking/lockdep.c:3039
 check_deadlock kernel/locking/lockdep.c:3091 [inline]
 validate_chain kernel/locking/lockdep.c:3893 [inline]
 __lock_acquire+0x6240/0x7904 kernel/locking/lockdep.c:5228
 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
 __mutex_lock_common+0x1f0/0x24b8 kernel/locking/mutex.c:585
 __mutex_lock kernel/locking/mutex.c:730 [inline]
 mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:782
 hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:458
 hfsplus_bmap_reserve+0xec/0x474 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x1e8/0x4ac fs/hfsplus/extents.c:104
 __hfsplus_ext_cache_extent+0x84/0xa84 fs/hfsplus/extents.c:186
 hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
 hfsplus_file_extend+0x39c/0x1544 fs/hfsplus/extents.c:462
 hfsplus_bmap_reserve+0xec/0x474 fs/hfsplus/btree.c:358
 hfsplus_create_attr+0x1b0/0x394 fs/hfsplus/attributes.c:221
 __hfsplus_setxattr+0x9c4/0x2334 fs/hfsplus/xattr.c:354
 hfsplus_initxattrs+0x194/0x250 fs/hfsplus/xattr_security.c:59
 security_inode_init_security+0x73c/0x908 security/security.c:1852
 hfsplus_init_security+0x40/0x54 fs/hfsplus/xattr_security.c:71
 hfsplus_fill_super+0x1064/0x16f8 fs/hfsplus/super.c:568
 get_tree_bdev_flags+0x38c/0x494 fs/super.c:1636
 get_tree_bdev+0x2c/0x3c fs/super.c:1659
 hfsplus_get_tree+0x28/0x38 fs/hfsplus/super.c:640
 vfs_get_tree+0x90/0x28c fs/super.c:1814
 do_new_mount+0x278/0x900 fs/namespace.c:3560
 path_mount+0x590/0xe04 fs/namespace.c:3887
 do_mount fs/namespace.c:3900 [inline]
 __do_sys_mount fs/namespace.c:4111 [inline]
 __se_sys_mount fs/namespace.c:4088 [inline]
 __arm64_sys_mount+0x4f4/0x5d0 fs/namespace.c:4088
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600