hfsplus: invalid length 1280 has been corrected to 255
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.4.124/6710 is trying to acquire lock:
ffff88802c01a2b8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264

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

locks held by syz.4.124/6710: 5, last CPU#0:
 #0: ffff888036e58510 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:494
 #1: ffff88802c01da88 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1069 [inline]
 #1: ffff88802c01da88 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3785 [inline]
 #1: ffff88802c01da88 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: __start_renaming+0x148/0x410 fs/namei.c:3878
 #2: ffff888033b700a0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x179/0x2e0 fs/hfsplus/bfind.c:29
 #3: ffff88802c01c478 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21c/0x1df0 fs/hfsplus/extents.c:457
 #4: ffff88803c1d00e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xa9/0xd30 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 0 UID: 0 PID: 6710 Comm: syz.4.124 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x27a/0x290 kernel/locking/lockdep.c:3085
 check_deadlock kernel/locking/lockdep.c:3137 [inline]
 validate_chain kernel/locking/lockdep.c:3939 [inline]
 __lock_acquire+0x25db/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __mutex_lock_common kernel/locking/rtmutex_api.c:561 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:580
 hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264
 block_read_full_folio+0x29f/0x810 fs/buffer.c:2308
 filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2520
 do_read_cache_folio+0x2bf/0x560 mm/filemap.c:4156
 do_read_cache_page mm/filemap.c:4222 [inline]
 read_cache_page+0x5d/0x170 mm/filemap.c:4231
 read_mapping_page include/linux/pagemap.h:1009 [inline]
 hfsplus_block_allocate+0xf7/0xd30 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0xb77/0x1df0 fs/hfsplus/extents.c:468
 hfsplus_bmap_reserve+0x170/0x590 fs/hfsplus/btree.c:512
 hfsplus_rename_cat+0x22c/0x1070 fs/hfsplus/catalog.c:446
 hfsplus_rename+0x145/0x280 fs/hfsplus/dir.c:596
 vfs_rename+0xbd9/0xef0 fs/namei.c:6208
 filename_renameat2+0x533/0x9b0 fs/namei.c:6326
 __do_sys_rename fs/namei.c:6370 [inline]
 __se_sys_rename+0x55/0x2c0 fs/namei.c:6366
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd100d0e159
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:00007fd0fef45028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fd100f96090 RCX: 00007fd100d0e159
RDX: 0000000000000000 RSI: 0000200000000c40 RDI: 0000200000000a00
RBP: 00007fd100da503b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd100f96128 R14: 00007fd100f96090 R15: 00007ffd02ad5498
 </TASK>