hfsplus: invalid length 2325 has been corrected to 255
hfsplus: invalid length 2325 has been corrected to 255
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.6.285/7975 is trying to acquire lock:
ffff8880609fe9f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:262

but task is already holding lock:
ffff8880609ff8f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21b/0x1dc0 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

5 locks held by syz.6.285/7975:
 #0: ffff88803598e480 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff8880609fe4d8 (&type->i_mutex_dir_key#23/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1074 [inline]
 #1: ffff8880609fe4d8 (&type->i_mutex_dir_key#23/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3787 [inline]
 #1: ffff8880609fe4d8 (&type->i_mutex_dir_key#23/1){+.+.}-{4:4}, at: __start_renaming+0x148/0x410 fs/namei.c:3880
 #2: ffff88804ea780a0 (&tree->tree_lock#2){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28
 #3: ffff8880609ff8f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21b/0x1dc0 fs/hfsplus/extents.c:455
 #4: ffff88803894d0e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xa7/0xce0 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 1 UID: 0 PID: 7975 Comm: syz.6.285 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x253f/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:534 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:553
 hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:262
 block_read_full_folio+0x29f/0x830 fs/buffer.c:2317
 filemap_read_folio+0x137/0x3b0 mm/filemap.c:2502
 do_read_cache_folio+0x2bf/0x560 mm/filemap.c:4107
 do_read_cache_page mm/filemap.c:4173 [inline]
 read_cache_page+0x5d/0x170 mm/filemap.c:4182
 read_mapping_page include/linux/pagemap.h:1011 [inline]
 hfsplus_block_allocate+0xf3/0xce0 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0xb21/0x1dc0 fs/hfsplus/extents.c:466
 hfsplus_bmap_reserve+0x183/0x5b0 fs/hfsplus/btree.c:510
 hfsplus_rename_cat+0x23b/0x1080 fs/hfsplus/catalog.c:458
 hfsplus_rename+0x145/0x280 fs/hfsplus/dir.c:602
 vfs_rename+0xa96/0xeb0 fs/namei.c:6054
 filename_renameat2+0x539/0x9c0 fs/namei.c:6172
 __do_sys_rename fs/namei.c:6216 [inline]
 __se_sys_rename+0x55/0x2c0 fs/namei.c:6212
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6fbeb7ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6fbcdce028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f6fbedf5fa0 RCX: 00007f6fbeb7ce59
RDX: 0000000000000000 RSI: 0000200000001900 RDI: 0000200000000140
RBP: 00007f6fbec12d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6fbedf6038 R14: 00007f6fbedf5fa0 R15: 00007fffcabe5a18
 </TASK>