loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.0/5317 is trying to acquire lock:
ffff888042588e88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x215/0x1d70 fs/hfsplus/extents.c:453

but task is already holding lock:
ffff888042588108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x215/0x1d70 fs/hfsplus/extents.c:453

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.0.0/5317:
 #0: ffff8880126fe420 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff888033552b78 (&type->i_mutex_dir_key#8){++++}-{4:4}, at: inode_lock include/linux/fs.h:1028 [inline]
 #1: ffff888033552b78 (&type->i_mutex_dir_key#8){++++}-{4:4}, at: vfs_removexattr+0x6c/0x230 fs/xattr.c:574
 #2: ffff888012bb20b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28
 #3: ffff888012bb00b0 (&tree->tree_lock/2){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28
 #4: ffff888042588108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x215/0x1d70 fs/hfsplus/extents.c:453
 #5: ffff88801f7f80b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28

stack backtrace:
CPU: 0 UID: 0 PID: 5317 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x253f/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0xf0/0x2e0 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/mutex.c:614 [inline]
 __mutex_lock+0x19f/0x1300 kernel/locking/mutex.c:776
 hfsplus_file_extend+0x215/0x1d70 fs/hfsplus/extents.c:453
 hfsplus_bmap_reserve+0x125/0x510 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x28d/0x5b0 fs/hfsplus/extents.c:104
 __hfsplus_ext_cache_extent+0x89/0xe30 fs/hfsplus/extents.c:186
 hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
 hfsplus_file_extend+0x4af/0x1d70 fs/hfsplus/extents.c:457
 hfsplus_bmap_reserve+0x125/0x510 fs/hfsplus/btree.c:358
 hfsplus_delete_attr+0x164/0x320 fs/hfsplus/attributes.c:383
 hfsplus_removexattr fs/hfsplus/xattr.c:843 [inline]
 __hfsplus_setxattr+0x78b/0x2610 fs/hfsplus/xattr.c:288
 __vfs_removexattr+0x431/0x470 fs/xattr.c:518
 __vfs_removexattr_locked+0xe2/0x280 fs/xattr.c:553
 vfs_removexattr+0x7f/0x230 fs/xattr.c:575
 removexattr fs/xattr.c:1010 [inline]
 filename_removexattr fs/xattr.c:1038 [inline]
 path_removexattrat+0x3d0/0x750 fs/xattr.c:1071
 __do_sys_removexattr fs/xattr.c:1083 [inline]
 __se_sys_removexattr fs/xattr.c:1080 [inline]
 __x64_sys_removexattr+0x62/0x70 fs/xattr.c:1080
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7c7eb9c799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7c7fb29fe8 EFLAGS: 00000246 ORIG_RAX: 00000000000000c5
RAX: ffffffffffffffda RBX: 00007f7c7ee15fa0 RCX: 00007f7c7eb9c799
RDX: 0000000000000000 RSI: 0000200000000180 RDI: 0000200000000140
RBP: 00007f7c7ec32bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7c7ee16038 R14: 00007f7c7ee15fa0 R15: 00007ffec256cf88
 </TASK>