syzbot

loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
5.15.179-syzkaller #0 Not tainted
--------------------------------------------
syz-executor296/4162 is trying to acquire lock:
ffff888026510e88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x37f/0x14e0 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff8880265122c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x30f/0xc70 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

4 locks held by syz-executor296/4162:
 #0: ffff8880252bc460 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff8880265124c0 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff8880265124c0 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: do_truncate+0x208/0x300 fs/open.c:63
 #2: ffff8880265122c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x30f/0xc70 fs/hfsplus/extents.c:577
 #3: ffff888077ea38f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xb7/0x4f0 fs/hfsplus/bitmap.c:182

stack backtrace:
CPU: 1 PID: 4162 Comm: syz-executor296 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:2946 [inline]
 check_deadlock kernel/locking/lockdep.c:2989 [inline]
 validate_chain+0x46d2/0x5930 kernel/locking/lockdep.c:3775
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1da/0x25a0 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+0x37f/0x14e0 fs/hfsplus/extents.c:260
 block_read_full_page+0x2f9/0xde0 fs/buffer.c:2290
 do_read_cache_page+0x752/0x1040 mm/filemap.c:-1
 read_mapping_page include/linux/pagemap.h:515 [inline]
 hfsplus_block_free+0x120/0x4f0 fs/hfsplus/bitmap.c:185
 hfsplus_free_extents+0x17a/0xae0 fs/hfsplus/extents.c:363
 hfsplus_file_truncate+0x871/0xc70 fs/hfsplus/extents.c:592
 hfsplus_setattr+0x1b9/0x280 fs/hfsplus/inode.c:267
 notify_change+0xc6d/0xf50 fs/attr.c:505
 do_truncate+0x21c/0x300 fs/open.c:65
 handle_truncate fs/namei.c:3265 [inline]
 do_open fs/namei.c:3612 [inline]
 path_openat+0x28a3/0x2f20 fs/namei.c:3742
 do_filp_open+0x21c/0x460 fs/namei.c:3769
 do_sys_openat2+0x13b/0x4f0 fs/open.c:1253
 do_sys_open fs/open.c:1269 [inline]
 __do_sys_creat fs/open.c:1345 [inline]
 __se_sys_creat fs/open.c:1339 [inline]
 __x64_sys_creat+0x11f/0x160 fs/open.c:1339
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fb18e77da99
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff8e55ec78 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb18e77da99
RDX: 00007fb18e77ccf0 RSI: 0000000000000121 RDI: 0000200000000f00
RBP: 00007fb18e7f15f0 R08: 000000000000065c R09: 000055555c86d4c0
R10: 00007fff8e55eb40 R11: 0000000000000246 R12: 00007fff8e55eca0
R13: 00007fff8e55eec8 R14: 431bde82d7b634db R15: 00007fb18e7c603b
 </TASK>
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent