====================================================== WARNING: possible circular locking dependency detected 6.16.0-syzkaller-00857-gced1b9e0392d #0 Not tainted ------------------------------------------------------ syz.3.1006/10073 is trying to acquire lock: ffff888031b200f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xe5/0xa40 fs/hfsplus/bitmap.c:35 but task is already holding lock: ffff88805faf4488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1ca/0x10f0 fs/hfsplus/extents.c:455 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 kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 hfsplus_get_block+0x272/0x9d0 fs/hfsplus/extents.c:260 block_read_full_folio+0x457/0x850 fs/buffer.c:2420 filemap_read_folio+0xc8/0x2a0 mm/filemap.c:2412 do_read_cache_folio+0x263/0x5c0 mm/filemap.c:3923 do_read_cache_page mm/filemap.c:3989 [inline] read_cache_page+0x5b/0x160 mm/filemap.c:3998 read_mapping_page include/linux/pagemap.h:993 [inline] hfsplus_block_allocate+0x144/0xa40 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x459/0x10f0 fs/hfsplus/extents.c:466 hfsplus_get_block+0x1a9/0x9d0 fs/hfsplus/extents.c:245 __block_write_begin_int+0x4f4/0x16d0 fs/buffer.c:2145 block_write_begin+0x9a/0x1d0 fs/buffer.c:2256 cont_write_begin+0x61b/0x950 fs/buffer.c:2594 hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48 page_symlink+0x3fc/0x4c0 fs/namei.c:5512 hfsplus_symlink+0xd3/0x2b0 fs/hfsplus/dir.c:449 vfs_symlink fs/namei.c:4730 [inline] vfs_symlink+0x403/0x680 fs/namei.c:4714 do_symlinkat+0x261/0x310 fs/namei.c:4756 __do_sys_symlink fs/namei.c:4777 [inline] __se_sys_symlink fs/namei.c:4775 [inline] __x64_sys_symlink+0x75/0x90 fs/namei.c:4775 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 hfsplus_block_allocate+0xe5/0xa40 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0x459/0x10f0 fs/hfsplus/extents.c:466 hfsplus_bmap_reserve+0x31f/0x420 fs/hfsplus/btree.c:358 hfsplus_create_cat+0x20d/0x10d0 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x16dc/0x1bd0 fs/hfsplus/super.c:559 get_tree_bdev_flags+0x38c/0x620 fs/super.c:1692 vfs_get_tree+0x8e/0x340 fs/super.c:1815 do_new_mount fs/namespace.c:3805 [inline] path_mount+0x1482/0x1fd0 fs/namespace.c:4120 do_mount fs/namespace.c:4133 [inline] __do_sys_mount fs/namespace.c:4344 [inline] __se_sys_mount fs/namespace.c:4321 [inline] __x64_sys_mount+0x28d/0x310 fs/namespace.c:4321 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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 *** 4 locks held by syz.3.1006/10073: #0: ffff888028c480e0 (&type->s_umount_key#75/1){+.+.}-{4:4}, at: alloc_super+0x235/0xbd0 fs/super.c:345 #1: ffff888031b20198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_fill_super+0x1665/0x1bd0 fs/hfsplus/super.c:552 #2: ffff8880783b00b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x17b/0x1f0 fs/hfsplus/bfind.c:28 #3: ffff88805faf4488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1ca/0x10f0 fs/hfsplus/extents.c:455 stack backtrace: CPU: 0 UID: 0 PID: 10073 Comm: syz.3.1006 Not tainted 6.16.0-syzkaller-00857-gced1b9e0392d #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2046 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 hfsplus_block_allocate+0xe5/0xa40 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0x459/0x10f0 fs/hfsplus/extents.c:466 hfsplus_bmap_reserve+0x31f/0x420 fs/hfsplus/btree.c:358 hfsplus_create_cat+0x20d/0x10d0 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x16dc/0x1bd0 fs/hfsplus/super.c:559 get_tree_bdev_flags+0x38c/0x620 fs/super.c:1692 vfs_get_tree+0x8e/0x340 fs/super.c:1815 do_new_mount fs/namespace.c:3805 [inline] path_mount+0x1482/0x1fd0 fs/namespace.c:4120 do_mount fs/namespace.c:4133 [inline] __do_sys_mount fs/namespace.c:4344 [inline] __se_sys_mount fs/namespace.c:4321 [inline] __x64_sys_mount+0x28d/0x310 fs/namespace.c:4321 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb348d9014a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 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:00007fb349b61e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007fb349b61ef0 RCX: 00007fb348d9014a RDX: 0000200000000000 RSI: 0000200000002380 RDI: 00007fb349b61eb0 RBP: 0000200000000000 R08: 00007fb349b61ef0 R09: 000000000080000c R10: 000000000080000c R11: 0000000000000246 R12: 0000200000002380 R13: 00007fb349b61eb0 R14: 00000000000006f6 R15: 0000200000000740 hfsplus: inconsistency in B*Tree (1,0,1,0,1) hfsplus: inconsistency in B*Tree (1,0,1,0,1)