============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz-executor/5597 is trying to acquire lock:
ffff888065e45f78 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264

but task is already holding lock:
ffff888065e43db8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2d0/0xd20 fs/hfsplus/extents.c:579

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-executor/5597: 6, last CPU#0:
 #0: ffff8880665a0510 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:494
 #1: ffff888065e45a88 (&type->i_mutex_dir_key#16/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1069 [inline]
 #1: ffff888065e45a88 (&type->i_mutex_dir_key#16/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2918 [inline]
 #1: ffff888065e45a88 (&type->i_mutex_dir_key#16/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2942 [inline]
 #1: ffff888065e45a88 (&type->i_mutex_dir_key#16/1){+.+.}-{4:4}, at: filename_unlinkat+0x2ad/0x610 fs/namei.c:5700
 #2: ffff888065e43f88 (&sb->s_type->i_mutex_key#43){++++}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #2: ffff888065e43f88 (&sb->s_type->i_mutex_key#43){++++}-{4:4}, at: vfs_unlink+0xd5/0x6e0 fs/namei.c:5635
 #3: ffff888063c1b978 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x18b/0x8e0 fs/hfsplus/dir.c:385
 #4: ffff888065e43db8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2d0/0xd20 fs/hfsplus/extents.c:579
 #5: ffff888063c1b8e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182

stack backtrace:
CPU: 0 UID: 0 PID: 5597 Comm: syz-executor 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_free+0x134/0x630 fs/hfsplus/bitmap.c:185
 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:364
 hfsplus_file_truncate+0x7ef/0xd20 fs/hfsplus/extents.c:595
 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1
 hfsplus_unlink+0x4e4/0x8e0 fs/hfsplus/dir.c:420
 vfs_unlink+0x27b/0x6e0 fs/namei.c:5649
 filename_unlinkat+0x3d3/0x610 fs/namei.c:5719
 __do_sys_unlink fs/namei.c:5754 [inline]
 __se_sys_unlink+0x2e/0x140 fs/namei.c:5751
 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:0x7f10077cd247
Code: 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe0d7eb078 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f10077cd247
RDX: 00007ffe0d7eb0a0 RSI: 00007ffe0d7eb130 RDI: 00007ffe0d7eb130
RBP: 00007ffe0d7eb130 R08: 00007ffe0d7ec130 R09: 00000000ffffffff
R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffe0d7ec220
R13: 00007f100786448b R14: 000000000005675f R15: 00007ffe0d7ed2f0
 </TASK>
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent: start 283, count 1
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent: start 260, count 3
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent: start 263, count 1
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent: start 264, count 1
hfsplus: invalid length 1280 has been corrected to 255