====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc7-syzkaller-00014-gd608703fcdd9 #0 Not tainted ------------------------------------------------------ syz.9.402/9288 is trying to acquire lock: ffff88807947b048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 but task is already holding lock: ffff8880538600b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x15a/0x1d0 fs/hfsplus/bfind.c:28 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&tree->tree_lock/1){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_find_init+0x15a/0x1d0 fs/hfsplus/bfind.c:28 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline] hfsplus_get_block+0x8dd/0x1530 fs/hfsplus/extents.c:268 __block_write_begin_int+0x6b2/0x1900 fs/buffer.c:2149 block_write_begin fs/buffer.c:2260 [inline] cont_write_begin+0x789/0xb50 fs/buffer.c:2599 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 cont_expand_zero fs/buffer.c:2559 [inline] cont_write_begin+0x825/0xb50 fs/buffer.c:2589 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 generic_perform_write+0x2c4/0x910 mm/filemap.c:4103 generic_file_write_iter+0x10f/0x540 mm/filemap.c:4246 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:684 ksys_pwrite64 fs/read_write.c:791 [inline] __do_sys_pwrite64 fs/read_write.c:799 [inline] __se_sys_pwrite64 fs/read_write.c:796 [inline] __x64_sys_pwrite64+0x193/0x220 fs/read_write.c:796 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 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_ext_read_extent fs/hfsplus/extents.c:218 [inline] hfsplus_file_extend+0x444/0x1990 fs/hfsplus/extents.c:462 hfsplus_get_block+0x411/0x1530 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6b2/0x1900 fs/buffer.c:2149 block_write_begin fs/buffer.c:2260 [inline] cont_write_begin+0x789/0xb50 fs/buffer.c:2599 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 cont_expand_zero fs/buffer.c:2526 [inline] cont_write_begin+0x2fa/0xb50 fs/buffer.c:2589 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 generic_perform_write+0x2c4/0x910 mm/filemap.c:4103 generic_file_write_iter+0x10f/0x540 mm/filemap.c:4246 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:684 ksys_pwrite64 fs/read_write.c:791 [inline] __do_sys_pwrite64 fs/read_write.c:799 [inline] __se_sys_pwrite64 fs/read_write.c:796 [inline] __x64_sys_pwrite64+0x193/0x220 fs/read_write.c:796 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 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(&tree->tree_lock/1); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock/1); lock(&HFSPLUS_I(inode)->extents_lock); *** DEADLOCK *** 4 locks held by syz.9.402/9288: #0: ffff888078ee2420 (sb_writers#27){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3041 [inline] #0: ffff888078ee2420 (sb_writers#27){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:680 #1: ffff88805d72b8f8 (&sb->s_type->i_mutex_key#31){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #1: ffff88805d72b8f8 (&sb->s_type->i_mutex_key#31){+.+.}-{4:4}, at: generic_file_write_iter+0xe3/0x540 mm/filemap.c:4243 #2: ffff88805d72b708 (&hip->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 #3: ffff8880538600b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x15a/0x1d0 fs/hfsplus/bfind.c:28 stack backtrace: CPU: 0 UID: 0 PID: 9288 Comm: syz.9.402 Not tainted 6.15.0-rc7-syzkaller-00014-gd608703fcdd9 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 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_ext_read_extent fs/hfsplus/extents.c:218 [inline] hfsplus_file_extend+0x444/0x1990 fs/hfsplus/extents.c:462 hfsplus_get_block+0x411/0x1530 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6b2/0x1900 fs/buffer.c:2149 block_write_begin fs/buffer.c:2260 [inline] cont_write_begin+0x789/0xb50 fs/buffer.c:2599 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 cont_expand_zero fs/buffer.c:2526 [inline] cont_write_begin+0x2fa/0xb50 fs/buffer.c:2589 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 generic_perform_write+0x2c4/0x910 mm/filemap.c:4103 generic_file_write_iter+0x10f/0x540 mm/filemap.c:4246 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:684 ksys_pwrite64 fs/read_write.c:791 [inline] __do_sys_pwrite64 fs/read_write.c:799 [inline] __se_sys_pwrite64 fs/read_write.c:796 [inline] __x64_sys_pwrite64+0x193/0x220 fs/read_write.c:796 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f30cb38e969 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:00007f30cc26e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000012 RAX: ffffffffffffffda RBX: 00007f30cb5b5fa0 RCX: 00007f30cb38e969 RDX: 0000000000000001 RSI: 00002000000002c0 RDI: 0000000000000008 RBP: 00007f30cb410ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000008080c61 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f30cb5b5fa0 R15: 00007ffea92f0b28