====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor/5599 is trying to acquire lock: ffff8880641350e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff88803dc56278 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2c6/0xce0 fs/hfsplus/extents.c:577 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/rtmutex_api.c:534 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:553 hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:262 block_read_full_folio+0x29f/0x830 fs/buffer.c:2317 filemap_read_folio+0x137/0x3b0 mm/filemap.c:2502 do_read_cache_folio+0x2bf/0x560 mm/filemap.c:4107 do_read_cache_page mm/filemap.c:4173 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4182 read_mapping_page include/linux/pagemap.h:1011 [inline] hfsplus_block_allocate+0xf3/0xce0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xb21/0x1dc0 fs/hfsplus/extents.c:466 hfsplus_get_block+0x42e/0x1670 fs/hfsplus/extents.c:247 __block_write_begin_int+0x6c6/0x1910 fs/buffer.c:2042 block_write_begin fs/buffer.c:2153 [inline] cont_write_begin+0x737/0xae0 fs/buffer.c:2491 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 page_symlink+0x27a/0x440 fs/namei.c:6402 hfsplus_symlink+0xd3/0x3a0 fs/hfsplus/dir.c:484 vfs_symlink+0x195/0x340 fs/namei.c:5643 filename_symlinkat+0x1cd/0x420 fs/namei.c:5668 __do_sys_symlink fs/namei.c:5695 [inline] __se_sys_symlink+0x4d/0x2b0 fs/namei.c:5691 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/0xf80 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 kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:534 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:553 hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:362 hfsplus_file_truncate+0x7aa/0xce0 fs/hfsplus/extents.c:593 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4f1/0x930 fs/hfsplus/dir.c:426 vfs_unlink+0x272/0x6d0 fs/namei.c:5498 filename_unlinkat+0x3d3/0x610 fs/namei.c:5568 __do_sys_unlink fs/namei.c:5603 [inline] __se_sys_unlink+0x2e/0x140 fs/namei.c:5600 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/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(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); *** DEADLOCK *** 5 locks held by syz-executor/5599: #0: ffff888031f82480 (sb_writers#32){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493 #1: ffff888038de1258 (&type->i_mutex_dir_key#21/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1074 [inline] #1: ffff888038de1258 (&type->i_mutex_dir_key#21/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2914 [inline] #1: ffff888038de1258 (&type->i_mutex_dir_key#21/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2938 [inline] #1: ffff888038de1258 (&type->i_mutex_dir_key#21/1){+.+.}-{4:4}, at: filename_unlinkat+0x2ad/0x610 fs/namei.c:5549 #2: ffff88803dc564d8 (&sb->s_type->i_mutex_key#38){++++}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline] #2: ffff88803dc564d8 (&sb->s_type->i_mutex_key#38){++++}-{4:4}, at: vfs_unlink+0xed/0x6d0 fs/namei.c:5484 #3: ffff888064135178 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x185/0x930 fs/hfsplus/dir.c:391 #4: ffff88803dc56278 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2c6/0xce0 fs/hfsplus/extents.c:577 stack backtrace: CPU: 0 UID: 0 PID: 5599 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/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/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:534 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:553 hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:362 hfsplus_file_truncate+0x7aa/0xce0 fs/hfsplus/extents.c:593 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4f1/0x930 fs/hfsplus/dir.c:426 vfs_unlink+0x272/0x6d0 fs/namei.c:5498 filename_unlinkat+0x3d3/0x610 fs/namei.c:5568 __do_sys_unlink fs/namei.c:5603 [inline] __se_sys_unlink+0x2e/0x140 fs/namei.c:5600 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0a555ebf47 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:00007ffcee4bbe68 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f0a555ebf47 RDX: 00007ffcee4bbe90 RSI: 00007ffcee4bbf20 RDI: 00007ffcee4bbf20 RBP: 00007ffcee4bbf20 R08: 00007ffcee4bcf20 R09: 00000000ffffffff R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffcee4bd010 R13: 00007f0a556821ca R14: 000000000007cc7c R15: 00007ffcee4be0e0