syzbot

loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/6077 is trying to acquire lock:
ffff88803c893cf8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff88803e372df8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 fs/hfsplus/extents.c:573

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.0.17/6077:
 #0: ffff888036a62480 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88803e373058 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: inode_lock_killable include/linux/fs.h:1033 [inline]
 #1: ffff88803e373058 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: do_truncate+0x18f/0x250 fs/open.c:63
 #2: ffff88803e372df8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 fs/hfsplus/extents.c:573
 #3: ffff888038b7b0e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182

stack backtrace:
CPU: 0 UID: 0 PID: 6077 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x253f/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
 hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:260
 block_read_full_folio+0x29f/0x830 fs/buffer.c:2421
 filemap_read_folio+0x137/0x3b0 mm/filemap.c:2496
 do_read_cache_folio+0x2bf/0x560 mm/filemap.c:4096
 do_read_cache_page mm/filemap.c:4162 [inline]
 read_cache_page+0x5d/0x170 mm/filemap.c:4171
 read_mapping_page include/linux/pagemap.h:1022 [inline]
 hfsplus_block_free+0x134/0x630 fs/hfsplus/bitmap.c:185
 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:360
 hfsplus_file_truncate+0x762/0xc30 fs/hfsplus/extents.c:588
 hfsplus_setattr+0x1c4/0x270 fs/hfsplus/inode.c:286
 notify_change+0xc18/0xf60 fs/attr.c:546
 do_truncate+0x1c2/0x250 fs/open.c:68
 handle_truncate fs/namei.c:4279 [inline]
 do_open fs/namei.c:4675 [inline]
 path_openat+0x2fbe/0x38a0 fs/namei.c:4830
 do_file_open+0x23e/0x4a0 fs/namei.c:4859
 do_sys_openat2+0x113/0x200 fs/open.c:1366
 do_sys_open fs/open.c:1372 [inline]
 __do_sys_creat fs/open.c:1450 [inline]
 __se_sys_creat fs/open.c:1444 [inline]
 __x64_sys_creat+0x8f/0xc0 fs/open.c:1444
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7b6d1ec629
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:00007ffe4ca35438 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f7b6d465fa0 RCX: 00007f7b6d1ec629
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00002000000000c0
RBP: 00007f7b6d282b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7b6d465fac R14: 00007f7b6d465fa0 R15: 00007f7b6d465fa0
 </TASK>
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent: start 131, count 2