====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc7-syzkaller-00002-gb36ddb9210e6 #0 Not tainted ------------------------------------------------------ syz-executor/5840 is trying to acquire lock: ffff88805910c8f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc3/0x4c0 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff88802f89a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb40 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}: 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_get_block+0x39e/0x1530 fs/hfsplus/extents.c:260 block_read_full_folio+0x29f/0x830 fs/buffer.c:2425 filemap_read_folio+0x117/0x380 mm/filemap.c:2401 do_read_cache_folio+0x354/0x590 mm/filemap.c:3885 do_read_cache_page mm/filemap.c:3951 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:3960 read_mapping_page include/linux/pagemap.h:989 [inline] hfsplus_block_allocate+0xff/0x8e0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xae3/0x1990 fs/hfsplus/extents.c:469 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 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_write+0x145/0x250 fs/read_write.c:736 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 (&sbi->alloc_mutex){+.+.}-{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_block_free+0xc3/0x4c0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x176/0xae0 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0x736/0xb40 fs/hfsplus/extents.c:592 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e3/0x730 fs/hfsplus/dir.c:405 vfs_unlink+0x394/0x650 fs/namei.c:4579 do_unlinkat+0x350/0x560 fs/namei.c:4643 __do_sys_unlink fs/namei.c:4689 [inline] __se_sys_unlink fs/namei.c:4687 [inline] __x64_sys_unlink+0x47/0x50 fs/namei.c:4687 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(&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/5840: #0: ffff888025aac420 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556 #1: ffff88802f899738 (&type->i_mutex_dir_key#18/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline] #1: ffff88802f899738 (&type->i_mutex_dir_key#18/1){+.+.}-{4:4}, at: do_unlinkat+0x1bf/0x560 fs/namei.c:4630 #2: ffff88802f89ab78 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #2: ffff88802f89ab78 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: vfs_unlink+0xf2/0x650 fs/namei.c:4568 #3: ffff88805910c998 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x160/0x730 fs/hfsplus/dir.c:370 #4: ffff88802f89a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb40 fs/hfsplus/extents.c:577 stack backtrace: CPU: 0 UID: 0 PID: 5840 Comm: syz-executor Not tainted 6.15.0-rc7-syzkaller-00002-gb36ddb9210e6 #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_block_free+0xc3/0x4c0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x176/0xae0 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0x736/0xb40 fs/hfsplus/extents.c:592 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e3/0x730 fs/hfsplus/dir.c:405 vfs_unlink+0x394/0x650 fs/namei.c:4579 do_unlinkat+0x350/0x560 fs/namei.c:4643 __do_sys_unlink fs/namei.c:4689 [inline] __se_sys_unlink fs/namei.c:4687 [inline] __x64_sys_unlink+0x47/0x50 fs/namei.c:4687 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:0x7f1a0138df17 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:00007ffc79e39d28 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1a0138df17 RDX: 00007ffc79e39d50 RSI: 00007ffc79e39de0 RDI: 00007ffc79e39de0 RBP: 00007ffc79e39de0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffc79e3aed0 R13: 00007f1a0141089d R14: 0000000000021dbf R15: 00007ffc79e3bfa0 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: invalid extended attribute record hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent