loop3: detected capacity change from 0 to 64
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.998/10894 is trying to acquire lock:
ffff8881129c00f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x1540

but task is already holding lock:
ffff8881121a80b0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&tree->tree_lock#2/1){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       hfs_find_init+0x18e/0x300
       hfs_get_block+0x51b/0xbd0
       block_read_full_folio+0x29f/0x830
       filemap_read_folio+0x117/0x380
       do_read_cache_folio+0x358/0x590
       read_cache_page+0x5d/0x170
       __hfs_bnode_create+0x4bb/0x960
       hfs_bnode_find+0x211/0xce0
       hfs_brec_find+0x172/0x510
       hfs_brec_read+0x24/0x110
       hfs_cat_find_brec+0x15c/0x3f0
       hfs_fill_super+0x4ae/0x6a0
       get_tree_bdev_flags+0x40e/0x4d0
       vfs_get_tree+0x92/0x2b0
       do_new_mount+0x302/0xa10
       __se_sys_mount+0x313/0x410
       do_syscall_64+0xfa/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       hfs_extend_file+0xda/0x1540
       hfs_bmap_reserve+0x107/0x430
       __hfs_ext_write_extent+0x1fa/0x470
       hfs_ext_write_extent+0x161/0x1e0
       hfs_write_inode+0xc6/0x8a0
       __writeback_single_inode+0x6f1/0xff0
       writeback_single_inode+0x1f9/0x6a0
       write_inode_now+0x160/0x1d0
       hfs_file_fsync+0xa4/0x140
       generic_file_write_iter+0x319/0x550
       vfs_write+0x5c9/0xb30
       ksys_write+0x145/0x250
       do_syscall_64+0xfa/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

4 locks held by syz.3.998/10894:
 #0: ffff88811183aef8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320
 #1: ffff888110b10420 (sb_writers#26){.+.+}-{0:0}, at: vfs_write+0x211/0xb30
 #2: ffff8881129c0fa0 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: hfs_file_fsync+0x9a/0x140
 #3: ffff8881121a80b0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300

stack backtrace:
CPU: 0 UID: 0 PID: 10894 Comm: syz.3.998 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_extend_file+0xda/0x1540
 hfs_bmap_reserve+0x107/0x430
 __hfs_ext_write_extent+0x1fa/0x470
 hfs_ext_write_extent+0x161/0x1e0
 hfs_write_inode+0xc6/0x8a0
 __writeback_single_inode+0x6f1/0xff0
 writeback_single_inode+0x1f9/0x6a0
 write_inode_now+0x160/0x1d0
 hfs_file_fsync+0xa4/0x140
 generic_file_write_iter+0x319/0x550
 vfs_write+0x5c9/0xb30
 ksys_write+0x145/0x250
 do_syscall_64+0xfa/0xfa0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8f3638efc9
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:00007f8f37237038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8f365e5fa0 RCX: 00007f8f3638efc9
RDX: 0000000000001006 RSI: 0000200000000940 RDI: 0000000000000005
RBP: 00007f8f36411f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8f365e6038 R14: 00007f8f365e5fa0 R15: 00007fff34c6e1e8
 </TASK>
