loop4: detected capacity change from 0 to 1024 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.87/4784 is trying to acquire lock: ffff88805519b0f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x99/0x8e0 fs/hfsplus/bitmap.c:35 but task is already holding lock: ffff888053088e88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1b3/0x1950 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){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_get_block+0x39b/0x1530 fs/hfsplus/extents.c:260 block_read_full_folio+0x3c9/0xed0 fs/buffer.c:2271 filemap_read_folio+0x160/0x760 mm/filemap.c:2490 do_read_cache_folio+0x2a0/0x760 mm/filemap.c:3627 do_read_cache_page+0x32/0x220 mm/filemap.c:3669 read_mapping_page include/linux/pagemap.h:791 [inline] hfsplus_block_allocate+0xfb/0x8e0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xa8e/0x1950 fs/hfsplus/extents.c:466 hfsplus_get_block+0x40e/0x1530 fs/hfsplus/extents.c:245 __block_write_begin_int+0x54b/0x1a70 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x96/0x1e0 fs/buffer.c:2102 cont_write_begin+0x5c4/0x7d0 fs/buffer.c:2456 hfsplus_write_begin+0x87/0xd0 fs/hfsplus/inode.c:52 page_symlink+0x23f/0x3c0 fs/namei.c:5240 hfsplus_symlink+0xc6/0x260 fs/hfsplus/dir.c:449 vfs_symlink+0x247/0x3d0 fs/namei.c:4479 do_symlinkat+0x1ae/0x3f0 fs/namei.c:4508 __do_sys_symlink fs/namei.c:4530 [inline] __se_sys_symlink fs/namei.c:4528 [inline] __x64_sys_symlink+0x7a/0x90 fs/namei.c:4528 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&sbi->alloc_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_block_allocate+0x99/0x8e0 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0xa8e/0x1950 fs/hfsplus/extents.c:466 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:358 hfsplus_create_cat+0x180/0x1020 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x12f6/0x1b90 fs/hfsplus/super.c:560 mount_bdev+0x287/0x3c0 fs/super.c:1443 legacy_get_tree+0xe6/0x180 fs/fs_context.c:632 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x24a/0xa40 fs/namespace.c:3078 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3606 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 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.4.87/4784: #0: ffff88804f70e0e0 (&type->s_umount_key#51/1){+.+.}-{3:3}, at: alloc_super+0x1fa/0x930 fs/super.c:228 #1: ffff88805519b198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_fill_super+0x1286/0x1b90 fs/hfsplus/super.c:553 #2: ffff88802f7460b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 #3: ffff888053088e88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1b3/0x1950 fs/hfsplus/extents.c:455 stack backtrace: CPU: 0 PID: 4784 Comm: syz.4.87 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 hfsplus_block_allocate+0x99/0x8e0 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0xa8e/0x1950 fs/hfsplus/extents.c:466 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:358 hfsplus_create_cat+0x180/0x1020 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x12f6/0x1b90 fs/hfsplus/super.c:560 mount_bdev+0x287/0x3c0 fs/super.c:1443 legacy_get_tree+0xe6/0x180 fs/fs_context.c:632 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x24a/0xa40 fs/namespace.c:3078 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3606 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fca88d9076a 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:00007fca89b91e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007fca89b91ef0 RCX: 00007fca88d9076a RDX: 0000200000000000 RSI: 0000200000002380 RDI: 00007fca89b91eb0 RBP: 0000200000000000 R08: 00007fca89b91ef0 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000002380 R13: 00007fca89b91eb0 R14: 00000000000006fe R15: 0000200000001400