====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor/6537 is trying to acquire lock: ffff0000cb7508f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xb8/0x3f8 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff0000f4dab048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x20c/0x970 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}: __mutex_lock_common+0x1d0/0x2678 kernel/locking/mutex.c:598 __mutex_lock kernel/locking/mutex.c:760 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812 hfsplus_get_block+0x2bc/0x1154 fs/hfsplus/extents.c:260 block_read_full_folio+0x2ec/0x824 fs/buffer.c:2420 hfsplus_read_folio+0x28/0x38 fs/hfsplus/inode.c:28 filemap_read_folio+0xec/0x2f8 mm/filemap.c:2413 do_read_cache_folio+0x364/0x5bc mm/filemap.c:3957 do_read_cache_page mm/filemap.c:4023 [inline] read_cache_page+0x6c/0x160 mm/filemap.c:4032 read_mapping_page include/linux/pagemap.h:985 [inline] hfsplus_block_allocate+0xdc/0x70c fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x770/0x1388 fs/hfsplus/extents.c:466 hfsplus_get_block+0x314/0x1154 fs/hfsplus/extents.c:245 __block_write_begin_int+0x53c/0x15e8 fs/buffer.c:2145 block_write_begin fs/buffer.c:2256 [inline] cont_write_begin+0x62c/0x968 fs/buffer.c:2594 hfsplus_write_begin+0x7c/0xc4 fs/hfsplus/inode.c:48 generic_perform_write+0x244/0x7bc mm/filemap.c:4175 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4292 generic_file_write_iter+0x10c/0x47c mm/filemap.c:4318 __kernel_write_iter+0x310/0x738 fs/read_write.c:619 __kernel_write+0xe0/0x130 fs/read_write.c:639 __dump_emit fs/coredump.c:1218 [inline] dump_emit+0x220/0x31c fs/coredump.c:1256 elf_core_dump+0x22f4/0x2f88 fs/binfmt_elf.c:2037 coredump_write+0x1080/0x1900 fs/coredump.c:1049 vfs_coredump+0x1844/0x23cc fs/coredump.c:1168 get_signal+0xe38/0x12f8 kernel/signal.c:3019 arch_do_signal_or_restart+0x1c0/0x4434 arch/arm64/kernel/signal.c:1619 exit_to_user_mode_loop+0x7c/0x168 kernel/entry/common.c:40 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] arm64_exit_to_user_mode arch/arm64/kernel/entry-common.c:103 [inline] el0_da+0x174/0x230 arch/arm64/kernel/entry-common.c:563 el0t_64_sync_handler+0x90/0x12c arch/arm64/kernel/entry-common.c:766 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 -> #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+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 __mutex_lock_common+0x1d0/0x2678 kernel/locking/mutex.c:598 __mutex_lock kernel/locking/mutex.c:760 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812 hfsplus_block_free+0xb8/0x3f8 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x10c/0x880 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x5e0/0x970 fs/hfsplus/extents.c:589 hfsplus_delete_inode+0x164/0x210 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x404/0x63c fs/hfsplus/dir.c:405 vfs_unlink+0x2e0/0x520 fs/namei.c:4586 do_unlinkat+0x2b8/0x488 fs/namei.c:4650 __do_sys_unlinkat fs/namei.c:4691 [inline] __se_sys_unlinkat fs/namei.c:4684 [inline] __arm64_sys_unlinkat+0xdc/0xf8 fs/namei.c:4684 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:763 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 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/6537: #0: ffff0000f4dbe428 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:557 #1: ffff0000f4da9df8 (&type->i_mutex_dir_key#9/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:915 [inline] #1: ffff0000f4da9df8 (&type->i_mutex_dir_key#9/1){+.+.}-{4:4}, at: do_unlinkat+0x190/0x488 fs/namei.c:4637 #2: ffff0000f4dab238 (&sb->s_type->i_mutex_key#27){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:870 [inline] #2: ffff0000f4dab238 (&sb->s_type->i_mutex_key#27){+.+.}-{4:4}, at: vfs_unlink+0xd0/0x520 fs/namei.c:4575 #3: ffff0000cb750998 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x140/0x63c fs/hfsplus/dir.c:370 #4: ffff0000f4dab048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x20c/0x970 fs/hfsplus/extents.c:574 stack backtrace: CPU: 1 UID: 0 PID: 6537 Comm: syz-executor Not tainted syzkaller #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043 check_noncircular+0x154/0x174 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+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 __mutex_lock_common+0x1d0/0x2678 kernel/locking/mutex.c:598 __mutex_lock kernel/locking/mutex.c:760 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812 hfsplus_block_free+0xb8/0x3f8 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x10c/0x880 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x5e0/0x970 fs/hfsplus/extents.c:589 hfsplus_delete_inode+0x164/0x210 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x404/0x63c fs/hfsplus/dir.c:405 vfs_unlink+0x2e0/0x520 fs/namei.c:4586 do_unlinkat+0x2b8/0x488 fs/namei.c:4650 __do_sys_unlinkat fs/namei.c:4691 [inline] __se_sys_unlinkat fs/namei.c:4684 [inline] __arm64_sys_unlinkat+0xdc/0xf8 fs/namei.c:4684 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:763 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 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