hfsplus: trying to free free bnode 0(1)
============================================
WARNING: possible recursive locking detected
5.15.180-syzkaller #0 Not tainted
--------------------------------------------
syz.2.79/4462 is trying to acquire lock:
ffff0000d91a1548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x2cc/0x11c8 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff0000cc8e0108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x210/0x984 fs/hfsplus/extents.c:577

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.2.79/4462:
 #0: ffff0000cddd0460 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff0000d91a1e00 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #1: ffff0000d91a1e00 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: do_unlinkat+0x18c/0x600 fs/namei.c:4331
 #2: ffff0000cc8e0300 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #2: ffff0000cc8e0300 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: vfs_unlink+0xd0/0x4f4 fs/namei.c:4269
 #3: ffff0000d22fa998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x140/0x664 fs/hfsplus/dir.c:370
 #4: ffff0000cc8e0108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x210/0x984 fs/hfsplus/extents.c:577
 #5: ffff0000d22fa8f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xb8/0x4a8 fs/hfsplus/bitmap.c:182

stack backtrace:
CPU: 1 PID: 4462 Comm: syz.2.79 Not tainted 5.15.180-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 __lock_acquire+0x18a4/0x651c kernel/locking/lockdep.c:-1
 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743
 hfsplus_get_block+0x2cc/0x11c8 fs/hfsplus/extents.c:260
 block_read_full_page+0x298/0xc40 fs/buffer.c:2290
 hfsplus_readpage+0x28/0x38 fs/hfsplus/inode.c:28
 do_read_cache_page+0x5f4/0x8f8 mm/filemap.c:-1
 read_cache_page+0x68/0x88 mm/filemap.c:3574
 read_mapping_page include/linux/pagemap.h:515 [inline]
 hfsplus_block_free+0x108/0x4a8 fs/hfsplus/bitmap.c:185
 hfsplus_free_extents+0x14c/0x8d8 fs/hfsplus/extents.c:363
 hfsplus_file_truncate+0x5e4/0x984 fs/hfsplus/extents.c:592
 hfsplus_delete_inode+0x164/0x210 fs/hfsplus/inode.c:-1
 hfsplus_unlink+0x3f8/0x664 fs/hfsplus/dir.c:405
 vfs_unlink+0x2e0/0x4f4 fs/namei.c:4280
 do_unlinkat+0x31c/0x600 fs/namei.c:4348
 __do_sys_unlinkat fs/namei.c:4391 [inline]
 __se_sys_unlinkat fs/namei.c:4384 [inline]
 __arm64_sys_unlinkat+0xe0/0xfc fs/namei.c:4384
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent