====================================================== WARNING: possible circular locking dependency detected 6.7.0-next-20240112-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/6124 is trying to acquire lock: ffff8880834080f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0xe9/0x990 fs/hfsplus/bitmap.c:35 but task is already holding lock: ffff88803eb6c488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:457 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:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_get_block+0x277/0x9e0 fs/hfsplus/extents.c:260 block_read_full_folio+0x38f/0xa70 fs/buffer.c:2382 filemap_read_folio+0xe9/0x2c0 mm/filemap.c:2324 do_read_cache_folio+0x209/0x550 mm/filemap.c:3703 do_read_cache_page mm/filemap.c:3769 [inline] read_cache_page+0x5b/0x160 mm/filemap.c:3778 read_mapping_page include/linux/pagemap.h:902 [inline] hfsplus_block_allocate+0x148/0x990 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x440/0x1090 fs/hfsplus/extents.c:468 hfsplus_get_block+0x1ae/0x9e0 fs/hfsplus/extents.c:245 __block_write_begin_int+0x4fb/0x16e0 fs/buffer.c:2103 __block_write_begin fs/buffer.c:2152 [inline] block_write_begin+0xb1/0x4a0 fs/buffer.c:2211 cont_write_begin+0x53d/0x740 fs/buffer.c:2565 hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:47 page_symlink+0x39a/0x4a0 fs/namei.c:5226 hfsplus_symlink+0xd3/0x2b0 fs/hfsplus/dir.c:449 vfs_symlink fs/namei.c:4478 [inline] vfs_symlink+0x3e8/0x630 fs/namei.c:4462 do_symlinkat+0x263/0x310 fs/namei.c:4504 __do_sys_symlink fs/namei.c:4525 [inline] __se_sys_symlink fs/namei.c:4523 [inline] __x64_sys_symlink+0x79/0xa0 fs/namei.c:4523 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6d/0x75 -> #0 (&sbi->alloc_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_block_allocate+0xe9/0x990 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0x440/0x1090 fs/hfsplus/extents.c:468 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x2b1/0x1240 fs/hfsplus/catalog.c:456 hfsplus_link+0x39d/0x770 fs/hfsplus/dir.c:323 vfs_link+0x83e/0xdf0 fs/namei.c:4602 do_linkat+0x553/0x600 fs/namei.c:4673 __do_sys_link fs/namei.c:4707 [inline] __se_sys_link fs/namei.c:4705 [inline] __x64_sys_link+0x81/0xa0 fs/namei.c:4705 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6d/0x75 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-executor.2/6124: #0: ffff888079278420 (sb_writers#16){.+.+}-{0:0}, at: filename_create+0x10d/0x530 fs/namei.c:3882 #1: ffff88803eb6dac0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] #1: ffff88803eb6dac0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: filename_create+0x1c2/0x530 fs/namei.c:3889 #2: ffff888084c48300 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline] #2: ffff888084c48300 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: vfs_link+0x652/0xdf0 fs/namei.c:4593 #3: ffff888083408198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_link+0x243/0x770 fs/hfsplus/dir.c:316 #4: ffff88807b6320b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x1a7/0x200 fs/hfsplus/bfind.c:30 #5: ffff88803eb6c488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c1/0x1090 fs/hfsplus/extents.c:457 stack backtrace: CPU: 0 PID: 6124 Comm: syz-executor.2 Not tainted 6.7.0-next-20240112-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 hfsplus_block_allocate+0xe9/0x990 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0x440/0x1090 fs/hfsplus/extents.c:468 hfsplus_bmap_reserve+0x31c/0x410 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x2b1/0x1240 fs/hfsplus/catalog.c:456 hfsplus_link+0x39d/0x770 fs/hfsplus/dir.c:323 vfs_link+0x83e/0xdf0 fs/namei.c:4602 do_linkat+0x553/0x600 fs/namei.c:4673 __do_sys_link fs/namei.c:4707 [inline] __se_sys_link fs/namei.c:4705 [inline] __x64_sys_link+0x81/0xa0 fs/namei.c:4705 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7f1fcbc7cda9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f1fcafff0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000056 RAX: ffffffffffffffda RBX: 00007f1fcbdabf80 RCX: 00007f1fcbc7cda9 RDX: 0000000000000000 RSI: 0000000020000bc0 RDI: 0000000020000100 RBP: 00007f1fcbcc947a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f1fcbdabf80 R15: 00007ffdc0eb99b8