======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.659/11375 is trying to acquire lock:
ffff88816d4a20b0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300

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

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}:
       __mutex_lock+0x187/0x1350
       hfs_extend_file+0xda/0x1540
       hfs_bmap_reserve+0x107/0x430
       __hfs_ext_write_extent+0x1fa/0x470
       __hfs_ext_cache_extent+0x6b/0x9b0
       hfs_extend_file+0x31e/0x1540
       hfs_get_block+0x3d7/0xbd0
       __block_write_begin_int+0x6b5/0x1900
       cont_write_begin+0x78c/0xb50
       hfs_write_begin+0x66/0xb0
       cont_write_begin+0x2fd/0xb50
       hfs_write_begin+0x66/0xb0
       hfs_file_truncate+0x19c/0xb30
       hfs_inode_setattr+0x4a9/0x670
       notify_change+0xc1a/0xf40
       do_truncate+0x1a4/0x220
       do_ftruncate+0x4a5/0x560
       __x64_sys_ftruncate+0x92/0xf0
       do_syscall_64+0xfa/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&tree->tree_lock#2/1){+.+.}-{4:4}:
       __lock_acquire+0x15a6/0x2cf0
       lock_acquire+0x117/0x340
       __mutex_lock+0x187/0x1350
       hfs_find_init+0x18e/0x300
       hfs_extend_file+0x2f6/0x1540
       hfs_bmap_reserve+0x107/0x430
       hfs_cat_create+0x1c5/0x770
       hfs_mkdir+0x6c/0xe0
       vfs_mkdir+0x512/0x5b0
       do_mkdirat+0x276/0x4b0
       __x64_sys_mkdirat+0x87/0xa0
       do_syscall_64+0xfa/0xf80
       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.5.659/11375:
 #0: ffff8881bd878420 (sb_writers#32){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888023dfdda0 (&type->i_mutex_dir_key#24/1){+.+.}-{4:4}, at: filename_create+0x1fb/0x360
 #2: ffff88816d4a40b0 (&tree->tree_lock#2){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300
 #3: ffff888023dfd578 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x1540

stack backtrace:
CPU: 0 UID: 0 PID: 11375 Comm: syz.5.659 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+0x2e2/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a6/0x2cf0
 lock_acquire+0x117/0x340
 __mutex_lock+0x187/0x1350
 hfs_find_init+0x18e/0x300
 hfs_extend_file+0x2f6/0x1540
 hfs_bmap_reserve+0x107/0x430
 hfs_cat_create+0x1c5/0x770
 hfs_mkdir+0x6c/0xe0
 vfs_mkdir+0x512/0x5b0
 do_mkdirat+0x276/0x4b0
 __x64_sys_mkdirat+0x87/0xa0
 do_syscall_64+0xfa/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa626d8df17
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:00007fa627b5ae68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fa627b5aef0 RCX: 00007fa626d8df17
RDX: 00000000000001ff RSI: 00002000000003c0 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00002000000003c0
R13: 00007fa627b5aeb0 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
