====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc4-syzkaller-00189-g2bfcee565c3a #0 Not tainted ------------------------------------------------------ syz.9.492/10156 is trying to acquire lock: ffff88804b5ad0f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0x9d/0x8e0 fs/hfsplus/bitmap.c:35 but task is already holding lock: ffff8880599922c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_get_block+0x39e/0x1530 fs/hfsplus/extents.c:260 block_read_full_folio+0x29c/0x830 fs/buffer.c:2427 filemap_read_folio+0x114/0x380 mm/filemap.c:2401 do_read_cache_folio+0x354/0x590 mm/filemap.c:3885 do_read_cache_page mm/filemap.c:3951 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:3960 read_mapping_page include/linux/pagemap.h:989 [inline] hfsplus_block_allocate+0xff/0x8e0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xae3/0x1990 fs/hfsplus/extents.c:469 hfsplus_get_block+0x411/0x1530 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6b2/0x1900 fs/buffer.c:2151 block_write_begin fs/buffer.c:2262 [inline] cont_write_begin+0x789/0xb50 fs/buffer.c:2601 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:46 generic_perform_write+0x2c4/0x910 mm/filemap.c:4103 generic_file_write_iter+0x10f/0x540 mm/filemap.c:4246 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x548/0xa90 fs/read_write.c:684 ksys_write+0x145/0x250 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 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:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_block_allocate+0x9d/0x8e0 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0xae3/0x1990 fs/hfsplus/extents.c:469 hfsplus_bmap_reserve+0x122/0x500 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x1aa/0xde0 fs/hfsplus/catalog.c:456 hfsplus_link+0x359/0x6a0 fs/hfsplus/dir.c:323 vfs_link+0x4ea/0x6e0 fs/namei.c:4847 do_linkat+0x272/0x560 fs/namei.c:4917 __do_sys_link fs/namei.c:4951 [inline] __se_sys_link fs/namei.c:4949 [inline] __x64_sys_link+0x82/0x90 fs/namei.c:4949 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 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 *** 6 locks held by syz.9.492/10156: #0: ffff88805bc64420 (sb_writers#34){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556 #1: ffff8880599938f8 (&type->i_mutex_dir_key#22/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline] #1: ffff8880599938f8 (&type->i_mutex_dir_key#22/1){+.+.}-{4:4}, at: filename_create+0x1f9/0x470 fs/namei.c:4132 #2: ffff88807b1feef8 (&sb->s_type->i_mutex_key#37){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #2: ffff88807b1feef8 (&sb->s_type->i_mutex_key#37){+.+.}-{4:4}, at: vfs_link+0x3b4/0x6e0 fs/namei.c:4838 #3: ffff88804b5ad198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_link+0x216/0x6a0 fs/hfsplus/dir.c:316 #4: ffff888052b100b0 (&tree->tree_lock#2){+.+.}-{4:4}, at: hfsplus_find_init+0x15a/0x1d0 fs/hfsplus/bfind.c:28 #5: ffff8880599922c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1fc/0x1990 fs/hfsplus/extents.c:458 stack backtrace: CPU: 0 UID: 0 PID: 10156 Comm: syz.9.492 Not tainted 6.15.0-rc4-syzkaller-00189-g2bfcee565c3a #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079 check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_block_allocate+0x9d/0x8e0 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0xae3/0x1990 fs/hfsplus/extents.c:469 hfsplus_bmap_reserve+0x122/0x500 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x1aa/0xde0 fs/hfsplus/catalog.c:456 hfsplus_link+0x359/0x6a0 fs/hfsplus/dir.c:323 vfs_link+0x4ea/0x6e0 fs/namei.c:4847 do_linkat+0x272/0x560 fs/namei.c:4917 __do_sys_link fs/namei.c:4951 [inline] __se_sys_link fs/namei.c:4949 [inline] __x64_sys_link+0x82/0x90 fs/namei.c:4949 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f993fb8e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f9940a95038 EFLAGS: 00000246 ORIG_RAX: 0000000000000056 RAX: ffffffffffffffda RBX: 00007f993fdb5fa0 RCX: 00007f993fb8e969 RDX: 0000000000000000 RSI: 0000200000000bc0 RDI: 0000200000000280 RBP: 00007f993fc10ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f993fdb5fa0 R15: 00007ffc6e55dbf8