====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.3/6332 is trying to acquire lock: ffff8880325c20e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xbe/0x550 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff88804d17f8f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb50 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){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 hfsplus_get_block+0x3a0/0x1530 fs/hfsplus/extents.c:260 block_read_full_folio+0x29c/0x830 fs/buffer.c:2420 filemap_read_folio+0x114/0x380 mm/filemap.c:2413 do_read_cache_folio+0x2ba/0x560 mm/filemap.c:3957 do_read_cache_page mm/filemap.c:4023 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4032 read_mapping_page include/linux/pagemap.h:985 [inline] hfsplus_block_allocate+0xe4/0x9b0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xae3/0x19a0 fs/hfsplus/extents.c:466 hfsplus_get_block+0x413/0x1530 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6b2/0x1900 fs/buffer.c:2145 block_write_begin fs/buffer.c:2256 [inline] cont_write_begin+0x789/0xb50 fs/buffer.c:2594 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 page_symlink+0x26f/0x430 fs/namei.c:5512 hfsplus_symlink+0xca/0x260 fs/hfsplus/dir.c:449 vfs_symlink+0x143/0x2f0 fs/namei.c:4730 do_symlinkat+0x1b1/0x3f0 fs/namei.c:4756 __do_sys_symlink fs/namei.c:4777 [inline] __se_sys_symlink fs/namei.c:4775 [inline] __x64_sys_symlink+0x7a/0x90 fs/namei.c:4775 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sbi->alloc_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 hfsplus_block_free+0xbe/0x550 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x10d/0xa60 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x736/0xb50 fs/hfsplus/extents.c:589 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e6/0x740 fs/hfsplus/dir.c:405 hfsplus_rename+0xcb/0x1c0 fs/hfsplus/dir.c:547 vfs_rename+0xbd7/0xf00 fs/namei.c:5129 do_renameat2+0x6ce/0xa80 fs/namei.c:5278 __do_sys_renameat2 fs/namei.c:5312 [inline] __se_sys_renameat2 fs/namei.c:5309 [inline] __x64_sys_renameat2+0xce/0xe0 fs/namei.c:5309 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 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(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); *** DEADLOCK *** 6 locks held by syz-executor.3/6332: #0: ffff8880501fc488 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557 #1: ffff88804d17b058 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:914 [inline] #1: ffff88804d17b058 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3272 [inline] #1: ffff88804d17b058 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: do_renameat2+0x3b9/0xa80 fs/namei.c:5224 #2: ffff88804d17ce58 (&sb->s_type->i_mutex_key#19){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline] #2: ffff88804d17ce58 (&sb->s_type->i_mutex_key#19){+.+.}-{4:4}, at: lock_two_nondirectories+0xe7/0x180 fs/inode.c:1232 #3: ffff88804d17fb58 (&sb->s_type->i_mutex_key#19/4){+.+.}-{4:4}, at: vfs_rename+0x6d8/0xf00 fs/namei.c:5100 #4: ffff8880325c2178 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x163/0x740 fs/hfsplus/dir.c:370 #5: ffff88804d17f8f8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb50 fs/hfsplus/extents.c:574 stack backtrace: CPU: 0 UID: 0 PID: 6332 Comm: syz-executor.3 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043 check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 hfsplus_block_free+0xbe/0x550 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x10d/0xa60 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x736/0xb50 fs/hfsplus/extents.c:589 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e6/0x740 fs/hfsplus/dir.c:405 hfsplus_rename+0xcb/0x1c0 fs/hfsplus/dir.c:547 vfs_rename+0xbd7/0xf00 fs/namei.c:5129 do_renameat2+0x6ce/0xa80 fs/namei.c:5278 __do_sys_renameat2 fs/namei.c:5312 [inline] __se_sys_renameat2 fs/namei.c:5309 [inline] __x64_sys_renameat2+0xce/0xe0 fs/namei.c:5309 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc8f231cda9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc8f169e0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000013c RAX: ffffffffffffffda RBX: 00007fc8f244bf80 RCX: 00007fc8f231cda9 RDX: 0000000000000004 RSI: 00000000200000c0 RDI: 0000000000000005 RBP: 00007fc8f236947a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fc8f244bf80 R15: 00007ffd1271a3c8