loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted
--------------------------------------------
syz-executor417/5078 is trying to acquire lock:
ffff888079e19548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x277/0x9e0 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff888079e187c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:457

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

5 locks held by syz-executor417/5078:
 #0: ffff888022b260e0 (&type->s_umount_key#42/1){+.+.}-{3:3}, at: alloc_super+0x23d/0xbd0 fs/super.c:343
 #1: ffff8880229a3998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_fill_super+0x1657/0x1bc0 fs/hfsplus/super.c:559
 #2: ffff8880230520b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x1a7/0x200 fs/hfsplus/bfind.c:30
 #3: ffff888079e187c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:457
 #4: ffff8880229a38f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0xe5/0x960 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 0 PID: 5078 Comm: syz-executor417 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x20e6/0x3b30 kernel/locking/lockdep.c:5137
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
 hfsplus_get_block+0x277/0x9e0 fs/hfsplus/extents.c:260
 block_read_full_folio+0x392/0xa70 fs/buffer.c:2384
 filemap_read_folio+0xec/0x2c0 mm/filemap.c:2333
 do_read_cache_folio+0x209/0x550 mm/filemap.c:3703
 do_read_cache_page mm/filemap.c:3769 [inline]
 read_cache_page+0x5b/0x160 mm/filemap.c:3778
 read_mapping_page include/linux/pagemap.h:888 [inline]
 hfsplus_block_allocate+0x143/0x960 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0x440/0x1090 fs/hfsplus/extents.c:468
 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358
 hfsplus_create_cat+0x213/0x10d0 fs/hfsplus/catalog.c:272
 hfsplus_fill_super+0x16ce/0x1bc0 fs/hfsplus/super.c:566
 mount_bdev+0x1e6/0x2d0 fs/super.c:1658
 legacy_get_tree+0x10c/0x220 fs/fs_context.c:662
 vfs_get_tree+0x92/0x380 fs/super.c:1779
 do_new_mount fs/namespace.c:3352 [inline]
 path_mount+0x14e6/0x1f20 fs/namespace.c:3679
 do_mount fs/namespace.c:3692 [inline]
 __do_sys_mount fs/namespace.c:3898 [inline]
 __se_sys_mount fs/namespace.c:3875 [inline]
 __x64_sys_mount+0x297/0x320 fs/namespace.c:3875
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd5/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7fccdeba4e2a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 3e 07 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe15e50968 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffe15e50980 RCX: 00007fccdeba4e2a
RDX: 00000000200000c0 RSI: 0000000020000080 RDI: 00007ffe15e50980
RBP: 0000000000000004 R08: 00007ffe15e509c0 R09: 000000000000069e
R10: 0000000000810808 R11: 0000000000000286 R12: 0000000000810808
R13: 00007ffe15e509c0 R14: 0000000000000003 R15: 0000000000080000
 </TASK>