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

but task is already holding lock:
ffff88810b31ef78 (&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_write_extent+0x161/0x1e0
       hfs_write_inode+0x91/0x7d0
       __writeback_single_inode+0x6f1/0xff0
       writeback_sb_inodes+0x6c7/0x1010
       wb_writeback+0x43b/0xaf0
       wb_workfn+0x409/0xef0
       process_scheduled_works+0xae1/0x17b0
       worker_thread+0x8a0/0xda0
       kthread+0x711/0x8a0
       ret_from_fork+0x3fc/0x770
       ret_from_fork_asm+0x1a/0x30

-> #0 (&tree->tree_lock/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_mkdir+0x6c/0x80
       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/1);
                               lock(&HFS_I(tree->inode)->extents_lock);
  lock(&tree->tree_lock/1);

 *** DEADLOCK ***

4 locks held by syz.9.1166/15792:
 #0: ffff88812a9bc428 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff88810b31b6a0 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0
 #2: ffff888120d8e0b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfs_find_init+0x184/0x200
 #3: ffff88810b31ef78 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x1230

stack backtrace:
CPU: 1 UID: 0 PID: 15792 Comm: syz.9.1166 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_mkdir+0x6c/0x80
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fecf398ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fecf4875038 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fecf3bc5fa0 RCX: 00007fecf398ebe9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00002000000004c0
RBP: 00007fecf3a11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fecf3bc6038 R14: 00007fecf3bc5fa0 R15: 00007fff1b2d4618
 </TASK>
