====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc2-syzkaller-gc72692105976 #0 Not tainted ------------------------------------------------------ syz-executor/6472 is trying to acquire lock: ffff0000f673c0f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xcc/0x414 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff0000d94507c8 (&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/0x2604 kernel/locking/mutex.c:601 __mutex_lock kernel/locking/mutex.c:746 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:798 hfsplus_get_block+0x2c4/0x1168 fs/hfsplus/extents.c:260 block_read_full_folio+0x2e8/0x824 fs/buffer.c:2392 hfsplus_read_folio+0x28/0x38 fs/hfsplus/inode.c:28 filemap_read_folio+0x108/0x318 mm/filemap.c:2400 do_read_cache_folio+0x368/0x5c0 mm/filemap.c:3884 do_read_cache_page mm/filemap.c:3950 [inline] read_cache_page+0x6c/0x15c mm/filemap.c:3959 read_mapping_page include/linux/pagemap.h:989 [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:2227 [inline] cont_write_begin+0x634/0x984 fs/buffer.c:2566 hfsplus_write_begin+0x7c/0xc4 fs/hfsplus/inode.c:46 generic_perform_write+0x280/0x894 mm/filemap.c:4102 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4219 generic_file_write_iter+0x108/0x4b4 mm/filemap.c:4245 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x704/0xa9c fs/read_write.c:684 ksys_write+0x15c/0x26c fs/read_write.c:736 __do_sys_write fs/read_write.c:747 [inline] __se_sys_write fs/read_write.c:744 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:744 __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:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x17b8/0x32c4 kernel/locking/lockdep.c:5235 lock_acquire+0x150/0x2e8 kernel/locking/lockdep.c:5866 __mutex_lock_common+0x1f0/0x2604 kernel/locking/mutex.c:601 __mutex_lock kernel/locking/mutex.c:746 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:798 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 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x42c/0x690 fs/hfsplus/dir.c:405 vfs_unlink+0x2f0/0x534 fs/namei.c:4544 do_unlinkat+0x468/0x698 fs/namei.c:4608 __do_sys_unlinkat fs/namei.c:4649 [inline] __se_sys_unlinkat fs/namei.c:4642 [inline] __arm64_sys_unlinkat+0xc8/0xf8 fs/namei.c:4642 __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-executor/6472: #0: ffff0000f46be420 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:556 #1: ffff0000f4641df8 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline] #1: ffff0000f4641df8 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: do_unlinkat+0x2dc/0x698 fs/namei.c:4595 #2: ffff0000d94509b8 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #2: ffff0000d94509b8 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: vfs_unlink+0xd8/0x534 fs/namei.c:4533 #3: ffff0000f673c198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x144/0x690 fs/hfsplus/dir.c:370 #4: ffff0000d94507c8 (&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: 6472 Comm: syz-executor Not tainted 6.15.0-rc2-syzkaller-gc72692105976 #0 PREEMPT 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/0x1028 lib/dump_stack.c:129 print_circular_bug+0x32c/0x334 kernel/locking/lockdep.c:2079 check_noncircular+0x15c/0x178 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 kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x17b8/0x32c4 kernel/locking/lockdep.c:5235 lock_acquire+0x150/0x2e8 kernel/locking/lockdep.c:5866 __mutex_lock_common+0x1f0/0x2604 kernel/locking/mutex.c:601 __mutex_lock kernel/locking/mutex.c:746 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:798 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 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x42c/0x690 fs/hfsplus/dir.c:405 vfs_unlink+0x2f0/0x534 fs/namei.c:4544 do_unlinkat+0x468/0x698 fs/namei.c:4608 __do_sys_unlinkat fs/namei.c:4649 [inline] __se_sys_unlinkat fs/namei.c:4642 [inline] __arm64_sys_unlinkat+0xc8/0xf8 fs/namei.c:4642 __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 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 syz-executor: attempt to access beyond end of device loop0: rw=2049, sector=45096, nr_sectors = 8 limit=40427 CPU: 1 UID: 0 PID: 6472 Comm: syz-executor Not tainted 6.15.0-rc2-syzkaller-gc72692105976 #0 PREEMPT 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/0x1028 lib/dump_stack.c:129 f2fs_handle_critical_error+0x380/0x534 fs/f2fs/super.c:4276 f2fs_stop_checkpoint+0x58/0x6c fs/f2fs/checkpoint.c:35 f2fs_write_end_io+0x99c/0xdb0 fs/f2fs/data.c:353 bio_endio+0x840/0x87c block/bio.c:1551 submit_bio_noacct+0x158/0x17cc block/blk-core.c:881 submit_bio+0x374/0x564 block/blk-core.c:916 f2fs_submit_write_bio+0x13c/0x36c fs/f2fs/data.c:528 __submit_merged_bio+0x258/0x79c fs/f2fs/data.c:543 __f2fs_submit_merged_write fs/f2fs/data.c:639 [inline] __submit_merged_write_cond+0x248/0x4e8 fs/f2fs/data.c:661 f2fs_submit_merged_write_cond fs/f2fs/data.c:678 [inline] f2fs_write_cache_pages fs/f2fs/data.c:3215 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3296 [inline] f2fs_write_data_pages+0x20fc/0x2acc fs/f2fs/data.c:3323 do_writepages+0x2f8/0x7c4 mm/page-writeback.c:2656 filemap_fdatawrite_wbc mm/filemap.c:386 [inline] __filemap_fdatawrite_range mm/filemap.c:419 [inline] __filemap_fdatawrite mm/filemap.c:425 [inline] filemap_fdatawrite+0x180/0x23c mm/filemap.c:430 f2fs_sync_dirty_inodes+0x2c0/0x7d4 fs/f2fs/checkpoint.c:1117 block_operations fs/f2fs/checkpoint.c:1257 [inline] f2fs_write_checkpoint+0x6c0/0x174c fs/f2fs/checkpoint.c:1652 kill_f2fs_super+0x220/0x590 fs/f2fs/super.c:5026 deactivate_locked_super+0xc4/0x12c fs/super.c:473 deactivate_super+0xe0/0x100 fs/super.c:506 cleanup_mnt+0x34c/0x3dc fs/namespace.c:1435 __cleanup_mnt+0x20/0x30 fs/namespace.c:1442 task_work_run+0x230/0x2e0 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] do_notify_resume+0x178/0x1f4 arch/arm64/kernel/entry-common.c:151 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline] el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:745 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 F2FS-fs (loop0): Stopped filesystem due to reason: 3