====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor/5803 is trying to acquire lock: ffff88803704d8e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc7/0x5f0 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff88805cea0ff8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2a4/0xc70 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}: 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+0x39a/0x15e0 fs/hfsplus/extents.c:260 block_read_full_folio+0x29f/0x830 fs/buffer.c:2420 filemap_read_folio+0x117/0x380 mm/filemap.c:2444 do_read_cache_folio+0x2ba/0x560 mm/filemap.c:4036 do_read_cache_page mm/filemap.c:4102 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4111 read_mapping_page include/linux/pagemap.h:993 [inline] hfsplus_block_allocate+0xf3/0xc40 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xa9a/0x1ba0 fs/hfsplus/extents.c:464 hfsplus_get_block+0x40c/0x15e0 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6b5/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 cont_expand_zero fs/buffer.c:2522 [inline] cont_write_begin+0x2fd/0xb50 fs/buffer.c:2584 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 generic_cont_expand_simple+0x13f/0x210 fs/buffer.c:2485 hfsplus_setattr+0x169/0x270 fs/hfsplus/inode.c:260 notify_change+0xc18/0xf60 fs/attr.c:546 do_truncate+0x1a4/0x220 fs/open.c:68 do_ftruncate+0x495/0x550 fs/open.c:195 do_sys_ftruncate fs/open.c:210 [inline] __do_sys_ftruncate fs/open.c:215 [inline] __se_sys_ftruncate fs/open.c:213 [inline] __x64_sys_ftruncate+0x92/0xf0 fs/open.c:213 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 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+0xc7/0x5f0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x754/0xc70 fs/hfsplus/extents.c:588 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e6/0x740 fs/hfsplus/dir.c:405 vfs_unlink+0x39a/0x660 fs/namei.c:4673 do_unlinkat+0x345/0x570 fs/namei.c:4737 __do_sys_unlink fs/namei.c:4783 [inline] __se_sys_unlink fs/namei.c:4781 [inline] __x64_sys_unlink+0x47/0x50 fs/namei.c:4781 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 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/5803: #0: ffff888027d14480 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499 #1: ffff888039682158 (&type->i_mutex_dir_key#19/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1025 [inline] #1: ffff888039682158 (&type->i_mutex_dir_key#19/1){+.+.}-{4:4}, at: do_unlinkat+0x1c7/0x570 fs/namei.c:4724 #2: ffff88805cea1258 (&sb->s_type->i_mutex_key#32){++++}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline] #2: ffff88805cea1258 (&sb->s_type->i_mutex_key#32){++++}-{4:4}, at: vfs_unlink+0xf2/0x660 fs/namei.c:4662 #3: ffff88803704d978 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x163/0x740 fs/hfsplus/dir.c:370 #4: ffff88805cea0ff8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2a4/0xc70 fs/hfsplus/extents.c:573 stack backtrace: CPU: 0 UID: 0 PID: 5803 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/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+0xc7/0x5f0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x754/0xc70 fs/hfsplus/extents.c:588 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e6/0x740 fs/hfsplus/dir.c:405 vfs_unlink+0x39a/0x660 fs/namei.c:4673 do_unlinkat+0x345/0x570 fs/namei.c:4737 __do_sys_unlink fs/namei.c:4783 [inline] __se_sys_unlink fs/namei.c:4781 [inline] __x64_sys_unlink+0x47/0x50 fs/namei.c:4781 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f37c65aecf7 Code: 73 01 c3 48 c7 c1 a8 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 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffcff883908 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f37c65aecf7 RDX: 00007ffcff883930 RSI: 00007ffcff8839c0 RDI: 00007ffcff8839c0 RBP: 00007ffcff8839c0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffcff884ab0 R13: 00007f37c6633d7d R14: 0000000000027833 R15: 00007ffcff885b80 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent: start 144, count 1 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent: start 131, count 2 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent: start 133, count 1