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

but task is already holding lock:
ffff0000dbce87c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x18c/0x13b4 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

7 locks held by syz.0.17/4488:
 #0: ffff0000dd1d0460 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402
 #1: ffff0000dbce9e00 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #1: ffff0000dbce9e00 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x3b8/0xa74 fs/namei.c:4974
 #2: ffff0000dbceb240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #2: ffff0000dbceb240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: lock_two_nondirectories+0xd0/0x128 fs/inode.c:1208
 #3: ffff0000dbceb900 (&sb->s_type->i_mutex_key#20/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #3: ffff0000dbceb900 (&sb->s_type->i_mutex_key#20/4){+.+.}-{3:3}, at: lock_two_nondirectories+0xb8/0x128 fs/inode.c:1210
 #4: ffff0000daee40b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc fs/hfsplus/bfind.c:28
 #5: ffff0000dbce87c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x18c/0x13b4 fs/hfsplus/extents.c:455
 #6: ffff0000ce19d8f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x88/0x7e4 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 1 PID: 4488 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call trace:
 dump_backtrace+0x1c0/0x1ec arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 __lock_acquire+0x15cc/0x6800 kernel/locking/lockdep.c:-1
 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662
 __mutex_lock_common+0x190/0x1f60 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
 hfsplus_get_block+0x2c0/0x11a0 fs/hfsplus/extents.c:260
 block_read_full_folio+0x2f4/0x980 fs/buffer.c:2271
 hfsplus_read_folio+0x28/0x38 fs/hfsplus/inode.c:28
 filemap_read_folio+0x134/0x384 mm/filemap.c:2490
 do_read_cache_folio+0x24c/0x538 mm/filemap.c:3659
 do_read_cache_page mm/filemap.c:3701 [inline]
 read_cache_page+0x6c/0x184 mm/filemap.c:3710
 read_mapping_page include/linux/pagemap.h:793 [inline]
 hfsplus_block_allocate+0xd8/0x7e4 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0x7a0/0x13b4 fs/hfsplus/extents.c:466
 hfsplus_bmap_reserve+0xe8/0x494 fs/hfsplus/btree.c:358
 hfsplus_rename_cat+0x1c8/0xdac fs/hfsplus/catalog.c:456
 hfsplus_rename+0x120/0x1dc fs/hfsplus/dir.c:552
 vfs_rename+0x95c/0xde0 fs/namei.c:4882
 do_renameat2+0x744/0xa74 fs/namei.c:5035
 __do_sys_renameat2 fs/namei.c:5068 [inline]
 __se_sys_renameat2 fs/namei.c:5065 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5065
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585