====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.972/6770 is trying to acquire lock: ffff88802f3460b0 (&tree->tree_lock#2/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 but task is already holding lock: ffff88807cb4c488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x28f/0xb30 fs/hfsplus/extents.c:574 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:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_file_extend+0x1b3/0x1950 fs/hfsplus/extents.c:455 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:358 __hfsplus_ext_write_extent+0x28d/0x5b0 fs/hfsplus/extents.c:104 __hfsplus_ext_cache_extent+0x89/0xe20 fs/hfsplus/extents.c:186 hfsplus_file_truncate+0x455/0xb30 fs/hfsplus/extents.c:597 hfsplus_setattr+0x1c0/0x280 fs/hfsplus/inode.c:269 notify_change+0xc74/0xf40 fs/attr.c:499 do_truncate+0x197/0x220 fs/open.c:65 vfs_truncate+0x262/0x2f0 fs/open.c:111 do_sys_truncate+0xdc/0x190 fs/open.c:134 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&tree->tree_lock#2/1){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x37e/0xb30 fs/hfsplus/extents.c:580 hfsplus_delete_inode+0x17c/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4c0/0x760 fs/hfsplus/dir.c:405 vfs_unlink+0x385/0x600 fs/namei.c:4330 do_unlinkat+0x324/0x560 fs/namei.c:4398 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4434 [inline] __x64_sys_unlinkat+0xd1/0xe0 fs/namei.c:4434 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 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 *** 5 locks held by syz.0.972/6770: #0: ffff888072a3c460 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff88807cb49080 (&type->i_mutex_dir_key#18/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #1: ffff88807cb49080 (&type->i_mutex_dir_key#18/1){+.+.}-{3:3}, at: do_unlinkat+0x178/0x560 fs/namei.c:4381 #2: ffff88807cb4c680 (&sb->s_type->i_mutex_key#32){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff88807cb4c680 (&sb->s_type->i_mutex_key#32){+.+.}-{3:3}, at: vfs_unlink+0xee/0x600 fs/namei.c:4319 #3: ffff888075d16198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x15a/0x760 fs/hfsplus/dir.c:370 #4: ffff88807cb4c488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x28f/0xb30 fs/hfsplus/extents.c:574 stack backtrace: CPU: 0 PID: 6770 Comm: syz.0.972 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x37e/0xb30 fs/hfsplus/extents.c:580 hfsplus_delete_inode+0x17c/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4c0/0x760 fs/hfsplus/dir.c:405 vfs_unlink+0x385/0x600 fs/namei.c:4330 do_unlinkat+0x324/0x560 fs/namei.c:4398 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4434 [inline] __x64_sys_unlinkat+0xd1/0xe0 fs/namei.c:4434 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f7d8158efc9 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:00007f7d824c5038 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007f7d817e6090 RCX: 00007f7d8158efc9 RDX: 0000000000000000 RSI: 00002000000001c0 RDI: ffffffffffffff9c RBP: 00007f7d81611f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f7d817e6128 R14: 00007f7d817e6090 R15: 00007ffdf91f7508