====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc7-syzkaller-ga2392f333575 #0 Not tainted ------------------------------------------------------ syz.2.432/8886 is trying to acquire lock: ffff0000f21230f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xcc/0x414 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff0000d80b87c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x24c/0xa18 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+0x1f0/0x24b8 kernel/locking/mutex.c:585 __mutex_lock kernel/locking/mutex.c:730 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:782 hfsplus_get_block+0x2c4/0x1168 fs/hfsplus/extents.c:260 block_read_full_folio+0x368/0x914 fs/buffer.c:2396 hfsplus_read_folio+0x28/0x38 fs/hfsplus/inode.c:28 filemap_read_folio+0x108/0x318 mm/filemap.c:2389 do_read_cache_folio+0x368/0x5c0 mm/filemap.c:3873 do_read_cache_page mm/filemap.c:3939 [inline] read_cache_page+0x6c/0x15c mm/filemap.c:3948 read_mapping_page include/linux/pagemap.h:1017 [inline] hfsplus_block_allocate+0xe4/0x728 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x7b4/0x1544 fs/hfsplus/extents.c:469 hfsplus_get_block+0x398/0x1168 fs/hfsplus/extents.c:245 __block_write_begin_int+0x4c4/0x1610 fs/buffer.c:2116 block_write_begin fs/buffer.c:2226 [inline] cont_write_begin+0x634/0x984 fs/buffer.c:2577 hfsplus_write_begin+0x7c/0xc4 fs/hfsplus/inode.c:46 generic_perform_write+0x29c/0x868 mm/filemap.c:4102 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4203 generic_file_write_iter+0x108/0x4b4 mm/filemap.c:4229 new_sync_write fs/read_write.c:586 [inline] vfs_write+0x704/0xa9c fs/read_write.c:679 ksys_write+0x15c/0x26c fs/read_write.c:731 __do_sys_write fs/read_write.c:742 [inline] __se_sys_write fs/read_write.c:739 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:739 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&sbi->alloc_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain kernel/locking/lockdep.c:3906 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5228 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851 __mutex_lock_common+0x1f0/0x24b8 kernel/locking/mutex.c:585 __mutex_lock kernel/locking/mutex.c:730 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:782 hfsplus_block_free+0xcc/0x414 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x148/0x8d4 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0x674/0xa18 fs/hfsplus/extents.c:592 hfsplus_delete_inode+0x154/0x200 hfsplus_unlink+0x42c/0x690 fs/hfsplus/dir.c:405 vfs_unlink+0x2f0/0x534 fs/namei.c:4525 do_unlinkat+0x4d4/0x704 fs/namei.c:4589 __do_sys_unlinkat fs/namei.c:4632 [inline] __se_sys_unlinkat fs/namei.c:4625 [inline] __arm64_sys_unlinkat+0xc8/0xf8 fs/namei.c:4625 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 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.2.432/8886: #0: ffff0000f9fcc420 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:547 #1: ffff0000d80b82f8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:912 [inline] #1: ffff0000d80b82f8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: do_unlinkat+0x2d8/0x704 fs/namei.c:4576 #2: ffff0000d80b89b8 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline] #2: ffff0000d80b89b8 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: vfs_unlink+0xd8/0x534 fs/namei.c:4514 #3: ffff0000f2123198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x144/0x690 fs/hfsplus/dir.c:370 #4: ffff0000d80b87c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x24c/0xa18 fs/hfsplus/extents.c:577 stack backtrace: CPU: 1 UID: 0 PID: 8886 Comm: syz.2.432 Not tainted 6.14.0-rc7-syzkaller-ga2392f333575 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2076 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2208 check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain kernel/locking/lockdep.c:3906 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5228 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851 __mutex_lock_common+0x1f0/0x24b8 kernel/locking/mutex.c:585 __mutex_lock kernel/locking/mutex.c:730 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:782 hfsplus_block_free+0xcc/0x414 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x148/0x8d4 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0x674/0xa18 fs/hfsplus/extents.c:592 hfsplus_delete_inode+0x154/0x200 hfsplus_unlink+0x42c/0x690 fs/hfsplus/dir.c:405 vfs_unlink+0x2f0/0x534 fs/namei.c:4525 do_unlinkat+0x4d4/0x704 fs/namei.c:4589 __do_sys_unlinkat fs/namei.c:4632 [inline] __se_sys_unlinkat fs/namei.c:4625 [inline] __arm64_sys_unlinkat+0xc8/0xf8 fs/namei.c:4625 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600