loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.6/5892 is trying to acquire lock:
ffff8880243d1548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x39f/0x1530 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff8880243d07c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1fd/0x1990 fs/hfsplus/extents.c:455

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

6 locks held by syz.0.6/5892:
 #0: ffff88807bde0418 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
 #1: ffff8880243d1e10 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #1: ffff8880243d1e10 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x427/0xc70 fs/namei.c:4972
 #2: ffff8880243d4690 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:839 [inline]
 #2: ffff8880243d4690 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: lock_two_inodes fs/inode.c:1172 [inline]
 #2: ffff8880243d4690 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: lock_two_nondirectories+0x1ab/0x270 fs/inode.c:1192
 #3: ffff8880242f40b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x154/0x1d0 fs/hfsplus/bfind.c:28
 #4: ffff8880243d07c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1fd/0x1990 fs/hfsplus/extents.c:455
 #5: ffff8880787d30f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x9d/0x8e0 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 0 PID: 5892 Comm: syz.0.6 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x5d40/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
 hfsplus_get_block+0x39f/0x1530 fs/hfsplus/extents.c:260
 block_read_full_folio+0x42e/0xf40 fs/buffer.c:2406
 filemap_read_folio+0x167/0x760 mm/filemap.c:2420
 do_read_cache_folio+0x470/0x7e0 mm/filemap.c:3789
 do_read_cache_page+0x32/0x250 mm/filemap.c:3855
 read_mapping_page include/linux/pagemap.h:892 [inline]
 hfsplus_block_allocate+0xff/0x8e0 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0xae4/0x1990 fs/hfsplus/extents.c:466
 hfsplus_bmap_reserve+0x122/0x500 fs/hfsplus/btree.c:358
 hfsplus_rename_cat+0x1aa/0xdb0 fs/hfsplus/catalog.c:456
 hfsplus_rename+0x128/0x1c0 fs/hfsplus/dir.c:552
 vfs_rename+0xb96/0xec0 fs/namei.c:4880
 do_renameat2+0x8a1/0xc70 fs/namei.c:5033
 __do_sys_rename fs/namei.c:5079 [inline]
 __se_sys_rename fs/namei.c:5077 [inline]
 __x64_sys_rename+0x86/0x90 fs/namei.c:5077
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f022418efc9
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:00007f02250cf038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f02243e5fa0 RCX: 00007f022418efc9
RDX: 0000000000000000 RSI: 0000200000000f40 RDI: 00002000000003c0
RBP: 00007f0224211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f02243e6038 R14: 00007f02243e5fa0 R15: 00007ffed875fad8
 </TASK>