loop3: detected capacity change from 0 to 1024
overlayfs: filesystem on './file0' not supported
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.3.85/4656 is trying to acquire lock:
ffff88802981b048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x39b/0x1530 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff88802981d8c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x2a0/0xb40 fs/hfsplus/extents.c:574

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.3.85/4656:
 #0: ffff888028a8e460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
 #1: ffff88802981c680 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #1: ffff88802981c680 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x1b9/0x6f0 fs/namei.c:4331
 #2: ffff88802981dac0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #2: ffff88802981dac0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_unlink+0xee/0x600 fs/namei.c:4269
 #3: ffff888024a5d998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x15a/0x760 fs/hfsplus/dir.c:370
 #4: ffff88802981d8c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x2a0/0xb40 fs/hfsplus/extents.c:574
 #5: ffff888024a5d8f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xc1/0x4d0 fs/hfsplus/bitmap.c:182

stack backtrace:
CPU: 1 PID: 4656 Comm: syz.3.85 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 __lock_acquire+0x1227/0x7c60 kernel/locking/lockdep.c:-1
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 hfsplus_get_block+0x39b/0x1530 fs/hfsplus/extents.c:260
 block_read_full_page+0x2e8/0xd10 fs/buffer.c:2290
 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1
 read_mapping_page include/linux/pagemap.h:515 [inline]
 hfsplus_block_free+0x125/0x4d0 fs/hfsplus/bitmap.c:185
 hfsplus_free_extents+0x10d/0xa50 fs/hfsplus/extents.c:360
 hfsplus_file_truncate+0x745/0xb40 fs/hfsplus/extents.c:589
 hfsplus_delete_inode+0x17c/0x230 fs/hfsplus/inode.c:-1
 hfsplus_unlink+0x4c0/0x760 fs/hfsplus/dir.c:405
 vfs_unlink+0x385/0x600 fs/namei.c:4280
 do_unlinkat+0x382/0x6f0 fs/namei.c:4348
 __do_sys_unlinkat fs/namei.c:4391 [inline]
 __se_sys_unlinkat fs/namei.c:4384 [inline]
 __x64_sys_unlinkat+0xd1/0xe0 fs/namei.c:4384
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3f39bafec9
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:00007f3f37e17038 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007f3f39e06fa0 RCX: 00007f3f39bafec9
RDX: 0000000000000000 RSI: 00002000000001c0 RDI: ffffffffffffff9c
RBP: 00007f3f39c32f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3f39e07038 R14: 00007f3f39e06fa0 R15: 00007ffc431b6268
 </TASK>
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent