loop5: detected capacity change from 0 to 1024 ====================================================== WARNING: possible circular locking dependency detected 6.10.0-syzkaller #0 Not tainted ------------------------------------------------------ syz.5.122/5649 is trying to acquire lock: ffff8880613ec0b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x886/0x9e0 fs/hfsplus/extents.c:595 but task is already holding lock: ffff888060b022c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x204/0x9e0 fs/hfsplus/extents.c:576 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:457 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x2b1/0x1240 fs/hfsplus/catalog.c:456 hfsplus_link+0x39d/0x770 fs/hfsplus/dir.c:323 vfs_link+0x841/0xe50 fs/namei.c:4619 do_linkat+0x533/0x5e0 fs/namei.c:4689 __do_sys_link fs/namei.c:4723 [inline] __se_sys_link fs/namei.c:4721 [inline] __x64_sys_link+0x81/0xa0 fs/namei.c:4721 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&tree->tree_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_file_truncate+0x886/0x9e0 fs/hfsplus/extents.c:595 hfsplus_delete_inode+0x18f/0x220 fs/hfsplus/inode.c:450 hfsplus_unlink+0x583/0x7f0 fs/hfsplus/dir.c:405 vfs_unlink+0x2fe/0x9b0 fs/namei.c:4349 do_unlinkat+0x5c0/0x750 fs/namei.c:4413 __do_sys_unlinkat fs/namei.c:4456 [inline] __se_sys_unlinkat fs/namei.c:4449 [inline] __x64_sys_unlinkat+0xc1/0x130 fs/namei.c:4449 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 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); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock); *** DEADLOCK *** 5 locks held by syz.5.122/5649: #0: ffff8880613ea420 (sb_writers#17){.+.+}-{0:0}, at: do_unlinkat+0x1d3/0x750 fs/namei.c:4396 #1: ffff888060b01e00 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:826 [inline] #1: ffff888060b01e00 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: do_unlinkat+0x288/0x750 fs/namei.c:4400 #2: ffff888060b024c0 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:791 [inline] #2: ffff888060b024c0 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: vfs_unlink+0xd3/0x9b0 fs/namei.c:4338 #3: ffff88805d164998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x184/0x7f0 fs/hfsplus/dir.c:370 #4: ffff888060b022c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x204/0x9e0 fs/hfsplus/extents.c:576 stack backtrace: CPU: 0 PID: 5649 Comm: syz.5.122 Not tainted 6.10.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_file_truncate+0x886/0x9e0 fs/hfsplus/extents.c:595 hfsplus_delete_inode+0x18f/0x220 fs/hfsplus/inode.c:450 hfsplus_unlink+0x583/0x7f0 fs/hfsplus/dir.c:405 vfs_unlink+0x2fe/0x9b0 fs/namei.c:4349 do_unlinkat+0x5c0/0x750 fs/namei.c:4413 __do_sys_unlinkat fs/namei.c:4456 [inline] __se_sys_unlinkat fs/namei.c:4449 [inline] __x64_sys_unlinkat+0xc1/0x130 fs/namei.c:4449 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f247cb75bd9 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:00007f247d8da048 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007f247cd03f60 RCX: 00007f247cb75bd9 RDX: 0000000000000000 RSI: 0000000020000280 RDI: 0000000000000004 RBP: 00007f247cbe4e60 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f247cd03f60 R15: 00007ffc023d62c8