loop3: detected capacity change from 0 to 1024
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.2849/16761 is trying to acquire lock:
ffff88803936e0b0 (&tree->tree_lock#2/1){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x290 fs/hfsplus/bfind.c:28

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760
       hfsplus_file_extend+0x1f8/0x1ba0 fs/hfsplus/extents.c:453
       hfsplus_bmap_reserve+0x122/0x500 fs/hfsplus/btree.c:358
       __hfsplus_ext_write_extent+0x28d/0x5b0 fs/hfsplus/extents.c:104
       __hfsplus_ext_cache_extent+0x89/0xe30 fs/hfsplus/extents.c:186
       hfsplus_file_truncate+0x467/0xc70 fs/hfsplus/extents.c:596
       hfsplus_setattr+0x1c4/0x270 fs/hfsplus/inode.c:266
       notify_change+0xc1a/0xf40 fs/attr.c:546
       do_truncate+0x1a4/0x220 fs/open.c:68
       vfs_truncate+0x493/0x520 fs/open.c:118
       do_sys_truncate+0xdb/0x190 fs/open.c:141
       __do_sys_truncate fs/open.c:153 [inline]
       __se_sys_truncate fs/open.c:151 [inline]
       __x64_sys_truncate+0x5b/0x70 fs/open.c:151
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&tree->tree_lock#2/1){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760
       hfsplus_find_init+0x168/0x290 fs/hfsplus/bfind.c:28
       hfsplus_file_truncate+0x388/0xc70 fs/hfsplus/extents.c:579
       hfsplus_setattr+0x1c4/0x270 fs/hfsplus/inode.c:266
       notify_change+0xc1a/0xf40 fs/attr.c:546
       do_truncate+0x1a4/0x220 fs/open.c:68
       vfs_truncate+0x493/0x520 fs/open.c:118
       do_sys_truncate+0xdb/0x190 fs/open.c:141
       __do_sys_truncate fs/open.c:153 [inline]
       __se_sys_truncate fs/open.c:151 [inline]
       __x64_sys_truncate+0x5b/0x70 fs/open.c:151
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&HFSPLUS_I(inode)->extents_lock);
                               lock(&tree->tree_lock#2/1);
                               lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&tree->tree_lock#2/1);

 *** DEADLOCK ***

3 locks held by syz.3.2849/16761:
 #0: ffff88803936c420 (sb_writers#25){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:508
 #1: ffff88804fca02f8 (&sb->s_type->i_mutex_key#31){+.+.}-{4:4}, at: inode_lock_killable include/linux/fs.h:985 [inline]
 #1: ffff88804fca02f8 (&sb->s_type->i_mutex_key#31){+.+.}-{4:4}, at: do_truncate+0x171/0x220 fs/open.c:63
 #2: ffff88804fca0108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2a4/0xc70 fs/hfsplus/extents.c:573

stack backtrace:
CPU: 1 UID: 0 PID: 16761 Comm: syz.3.2849 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043
 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/mutex.c:598 [inline]
 __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760
 hfsplus_find_init+0x168/0x290 fs/hfsplus/bfind.c:28
 hfsplus_file_truncate+0x388/0xc70 fs/hfsplus/extents.c:579
 hfsplus_setattr+0x1c4/0x270 fs/hfsplus/inode.c:266
 notify_change+0xc1a/0xf40 fs/attr.c:546
 do_truncate+0x1a4/0x220 fs/open.c:68
 vfs_truncate+0x493/0x520 fs/open.c:118
 do_sys_truncate+0xdb/0x190 fs/open.c:141
 __do_sys_truncate fs/open.c:153 [inline]
 __se_sys_truncate fs/open.c:151 [inline]
 __x64_sys_truncate+0x5b/0x70 fs/open.c:151
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f697518efc9
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:00007f697601f038 EFLAGS: 00000246 ORIG_RAX: 000000000000004c
RAX: ffffffffffffffda RBX: 00007f69753e5fa0 RCX: 00007f697518efc9
RDX: 0000000000000000 RSI: 0200000080000000 RDI: 0000200000000080
RBP: 00007f6975211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f69753e6038 R14: 00007f69753e5fa0 R15: 00007ffe167e6e98
 </TASK>