====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor/7252 is trying to acquire lock: ffff888024ab00b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28 but task is already holding lock: ffff88801bb222c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 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}: __mutex_lock_common kernel/locking/mutex.c:614 [inline] __mutex_lock+0x19f/0x1300 kernel/locking/mutex.c:776 hfsplus_file_extend+0x215/0x1d70 fs/hfsplus/extents.c:453 hfsplus_bmap_reserve+0x125/0x510 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_ext_read_extent fs/hfsplus/extents.c:218 [inline] hfsplus_file_extend+0x4af/0x1d70 fs/hfsplus/extents.c:457 hfsplus_get_block+0x42c/0x1670 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6c6/0x1910 fs/buffer.c:2143 block_write_begin fs/buffer.c:2254 [inline] cont_write_begin+0x737/0xae0 fs/buffer.c:2592 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 generic_perform_write+0x2e2/0x8f0 mm/filemap.c:4314 generic_file_write_iter+0x14a/0x680 mm/filemap.c:4457 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x61d/0xb90 fs/read_write.c:688 ksys_write+0x150/0x270 fs/read_write.c:740 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 -> #0 (&tree->tree_lock/1){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/mutex.c:614 [inline] __mutex_lock+0x19f/0x1300 kernel/locking/mutex.c:776 hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x39b/0xc30 fs/hfsplus/extents.c:579 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4ee/0x930 fs/hfsplus/dir.c:426 vfs_unlink+0x272/0x6c0 fs/namei.c:5470 filename_unlinkat+0x3cd/0x610 fs/namei.c:5540 __do_sys_unlink fs/namei.c:5575 [inline] __se_sys_unlink+0x2e/0x140 fs/namei.c:5572 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 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock/1); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock/1); *** DEADLOCK *** 5 locks held by syz-executor/7252: #0: ffff888032840420 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493 #1: ffff88801bb23238 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline] #1: ffff88801bb23238 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline] #1: ffff88801bb23238 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline] #1: ffff88801bb23238 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: filename_unlinkat+0x2a7/0x610 fs/namei.c:5521 #2: ffff88801bb224b8 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1028 [inline] #2: ffff88801bb224b8 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: vfs_unlink+0xed/0x6c0 fs/namei.c:5456 #3: ffff888032ad1198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x182/0x930 fs/hfsplus/dir.c:391 #4: ffff88801bb222c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 fs/hfsplus/extents.c:573 stack backtrace: CPU: 0 UID: 0 PID: 7252 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 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 kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/mutex.c:614 [inline] __mutex_lock+0x19f/0x1300 kernel/locking/mutex.c:776 hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x39b/0xc30 fs/hfsplus/extents.c:579 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4ee/0x930 fs/hfsplus/dir.c:426 vfs_unlink+0x272/0x6c0 fs/namei.c:5470 filename_unlinkat+0x3cd/0x610 fs/namei.c:5540 __do_sys_unlink fs/namei.c:5575 [inline] __se_sys_unlink+0x2e/0x140 fs/namei.c:5572 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:0x7f301259b067 Code: 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 RSP: 002b:00007ffc6f109a08 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f301259b067 RDX: 00007ffc6f109a30 RSI: 00007ffc6f109ac0 RDI: 00007ffc6f109ac0 RBP: 00007ffc6f109ac0 R08: 00007ffc6f10aac0 R09: 00000000ffffffff R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffc6f10abb0 R13: 00007f3012631c3b R14: 000000000004a0e8 R15: 00007ffc6f10bc80