loop5: detected capacity change from 0 to 1024
======================================================
WARNING: possible circular locking dependency detected
6.1.33-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.5/24513 is trying to acquire lock:
ffff8880807f80b0 (&tree->tree_lock/2){+.+.}-{3:3}, at: hfsplus_find_init+0x146/0x1c0

but task is already holding lock:
ffff888076d560b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x146/0x1c0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&tree->tree_lock){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
       __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       hfsplus_file_truncate+0x80d/0xb40 fs/hfsplus/extents.c:595
       hfsplus_setattr+0x1b9/0x280 fs/hfsplus/inode.c:269
       notify_change+0xdcd/0x1080 fs/attr.c:482
       do_truncate+0x21c/0x300 fs/open.c:65
       vfs_truncate+0x2dd/0x3a0 fs/open.c:111
       do_sys_truncate+0xda/0x190 fs/open.c:134
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
       __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       hfsplus_get_block+0x37f/0x14e0 fs/hfsplus/extents.c:260
       block_read_full_folio+0x403/0xf60 fs/buffer.c:2271
       filemap_read_folio+0x199/0x780 mm/filemap.c:2407
       do_read_cache_folio+0x2ee/0x810 mm/filemap.c:3535
       do_read_cache_page+0x32/0x220 mm/filemap.c:3577
       read_mapping_page include/linux/pagemap.h:756 [inline]
       __hfs_bnode_create+0x483/0x770 fs/hfsplus/bnode.c:440
       hfsplus_bnode_find+0x233/0x10b0 fs/hfsplus/bnode.c:486
       hfsplus_brec_find+0x17f/0x570 fs/hfsplus/bfind.c:183
       __hfsplus_getxattr+0x360/0xb10 fs/hfsplus/xattr.c:522
       hfsplus_getxattr+0x98/0xd0 fs/hfsplus/xattr.c:590
       vfs_getxattr_alloc+0x449/0x590 fs/xattr.c:380
       ima_read_xattr+0x35/0x60 security/integrity/ima/ima_appraise.c:228
       process_measurement+0xe38/0x1cf0 security/integrity/ima/ima_main.c:319
       ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520
       do_open fs/namei.c:3559 [inline]
       path_openat+0x2687/0x2e60 fs/namei.c:3714
       do_filp_open+0x230/0x480 fs/namei.c:3741
       do_sys_openat2+0x13b/0x500 fs/open.c:1318
       do_sys_open fs/open.c:1334 [inline]
       __do_sys_openat fs/open.c:1350 [inline]
       __se_sys_openat fs/open.c:1345 [inline]
       __x64_sys_openat+0x243/0x290 fs/open.c:1345
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&tree->tree_lock/2){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3098 [inline]
       check_prevs_add kernel/locking/lockdep.c:3217 [inline]
       validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
       __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       hfsplus_find_init+0x146/0x1c0
       hfsplus_delete_all_attrs+0x107/0x3c0 fs/hfsplus/attributes.c:366
       hfsplus_delete_cat+0xb83/0xfb0 fs/hfsplus/catalog.c:425
       hfsplus_rmdir+0xf1/0x1b0 fs/hfsplus/dir.c:425
       vfs_rmdir+0x35b/0x4b0 fs/namei.c:4121
       do_rmdir+0x362/0x670 fs/namei.c:4182
       __do_sys_unlinkat fs/namei.c:4362 [inline]
       __se_sys_unlinkat fs/namei.c:4356 [inline]
       __x64_sys_unlinkat+0xdc/0xf0 fs/namei.c:4356
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &tree->tree_lock/2 --> &HFSPLUS_I(inode)->extents_lock --> &tree->tree_lock

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

5 locks held by syz-executor.5/24513:
 #0: ffff888076d54460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
 #1: ffff888077a2c680 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
 #1: ffff888077a2c680 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: do_rmdir+0x21f/0x670 fs/namei.c:4169
 #2: ffff888077a2dac0 (&sb->s_type->i_mutex_key#32){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #2: ffff888077a2dac0 (&sb->s_type->i_mutex_key#32){+.+.}-{3:3}, at: vfs_rmdir+0xf9/0x4b0 fs/namei.c:4110
 #3: ffff88807bff2198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_rmdir+0xbd/0x1b0 fs/hfsplus/dir.c:424
 #4: ffff888076d560b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x146/0x1c0

stack backtrace:
CPU: 1 PID: 24513 Comm: syz-executor.5 Not tainted 6.1.33-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3098 [inline]
 check_prevs_add kernel/locking/lockdep.c:3217 [inline]
 validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
 __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 hfsplus_find_init+0x146/0x1c0
 hfsplus_delete_all_attrs+0x107/0x3c0 fs/hfsplus/attributes.c:366
 hfsplus_delete_cat+0xb83/0xfb0 fs/hfsplus/catalog.c:425
 hfsplus_rmdir+0xf1/0x1b0 fs/hfsplus/dir.c:425
 vfs_rmdir+0x35b/0x4b0 fs/namei.c:4121
 do_rmdir+0x362/0x670 fs/namei.c:4182
 __do_sys_unlinkat fs/namei.c:4362 [inline]
 __se_sys_unlinkat fs/namei.c:4356 [inline]
 __x64_sys_unlinkat+0xdc/0xf0 fs/namei.c:4356
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4f4ca8c199
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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:00007f4f4d8a9168 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007f4f4cbabf80 RCX: 00007f4f4ca8c199
RDX: 0000000000000200 RSI: 0000000020000940 RDI: 0000000000000004
RBP: 00007f4f4cae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc1f1cfe7f R14: 00007f4f4d8a9300 R15: 0000000000022000
 </TASK>