loop0: detected capacity change from 0 to 64
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.1222/10510 is trying to acquire lock:
ffff88801af9a0b0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfs_find_init+0x184/0x200

but task is already holding lock:
ffff88803250f5f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x1230

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       hfs_extend_file+0xda/0x1230
       hfs_bmap_reserve+0x107/0x430
       __hfs_ext_write_extent+0x1fa/0x470
       __hfs_ext_cache_extent+0x6b/0x9b0
       hfs_extend_file+0x316/0x1230
       hfs_get_block+0x3d7/0xbd0
       __block_write_begin_int+0x6b5/0x1900
       cont_write_begin+0x789/0xb50
       hfs_write_begin+0x66/0xb0
       generic_perform_write+0x2c5/0x900
       generic_file_write_iter+0x117/0x550
       vfs_write+0x5c9/0xb30
       ksys_write+0x145/0x250
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&tree->tree_lock#2/1){+.+.}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       hfs_find_init+0x184/0x200
       hfs_extend_file+0x2ee/0x1230
       hfs_bmap_reserve+0x107/0x430
       hfs_cat_create+0x1b3/0x640
       hfs_mkdir+0x6c/0xe0
       vfs_mkdir+0x306/0x510
       do_mkdirat+0x247/0x590
       __x64_sys_mkdirat+0x87/0xa0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&HFS_I(tree->inode)->extents_lock);
                               lock(&tree->tree_lock#2/1);
                               lock(&HFS_I(tree->inode)->extents_lock);
  lock(&tree->tree_lock#2/1);

 *** DEADLOCK ***

4 locks held by syz.0.1222/10510:
 #0: ffff8880327e6428 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff88803250d0a0 (&type->i_mutex_dir_key#16/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0
 #2: ffff88802fe1e0b0 (&tree->tree_lock#2){+.+.}-{4:4}, at: hfs_find_init+0x184/0x200
 #3: ffff88803250f5f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x1230

stack backtrace:
CPU: 0 UID: 0 PID: 10510 Comm: syz.0.1222 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250
 print_circular_bug+0x2ee/0x310
 check_noncircular+0x134/0x160
 validate_chain+0xb9b/0x2140
 __lock_acquire+0xab9/0xd20
 lock_acquire+0x120/0x360
 __mutex_lock+0x187/0x1350
 hfs_find_init+0x184/0x200
 hfs_extend_file+0x2ee/0x1230
 hfs_bmap_reserve+0x107/0x430
 hfs_cat_create+0x1b3/0x640
 hfs_mkdir+0x6c/0xe0
 vfs_mkdir+0x306/0x510
 do_mkdirat+0x247/0x590
 __x64_sys_mkdirat+0x87/0xa0
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5603d8d457
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5604c5ee68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f5604c5eef0 RCX: 00007f5603d8d457
RDX: 00000000000001ff RSI: 00002000000001c0 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f5604c5eeb0 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
