====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc5-syzkaller-17295-g1dc22be1f91f #0 Not tainted ------------------------------------------------------ syz-executor.4/8910 is trying to acquire lock: ffff0001221218f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0x54/0x740 fs/hfs/extent.c:397 but task is already holding lock: ffff00011bff00b0 (&tree->tree_lock#2/1){+.+.}-{3:3}, at: hfs_find_init+0xac/0xcc which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&tree->tree_lock#2/1){+.+.}-{3:3}: __mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 hfs_find_init+0xac/0xcc hfs_ext_read_extent fs/hfs/extent.c:200 [inline] hfs_extend_file+0x120/0x740 fs/hfs/extent.c:401 hfs_bmap_reserve+0x44/0xe8 fs/hfs/btree.c:234 hfs_cat_create+0xd4/0x358 fs/hfs/catalog.c:104 hfs_create+0x54/0xc8 fs/hfs/dir.c:202 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x804/0x11f0 fs/namei.c:3711 do_filp_open+0xdc/0x1b8 fs/namei.c:3741 do_sys_openat2+0xb8/0x22c fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_openat fs/open.c:1342 [inline] __se_sys_openat fs/open.c:1337 [inline] __arm64_sys_openat+0xb0/0xe0 fs/open.c:1337 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x104 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 -> #0 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055 lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668 __mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 hfs_extend_file+0x54/0x740 fs/hfs/extent.c:397 hfs_bmap_reserve+0x44/0xe8 fs/hfs/btree.c:234 __hfs_ext_write_extent+0xb8/0x138 fs/hfs/extent.c:121 __hfs_ext_cache_extent+0x58/0x1f0 fs/hfs/extent.c:174 hfs_ext_read_extent fs/hfs/extent.c:202 [inline] hfs_extend_file+0x14c/0x740 fs/hfs/extent.c:401 hfs_get_block+0x1c8/0x4c4 fs/hfs/extent.c:353 __block_write_begin_int+0x23c/0x9d4 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x74/0x14c fs/buffer.c:2102 cont_write_begin+0xf4/0x11c fs/buffer.c:2456 hfs_write_begin+0x64/0xac fs/hfs/inode.c:58 generic_perform_write+0xf0/0x2cc mm/filemap.c:3772 __generic_file_write_iter+0xd8/0x21c mm/filemap.c:3900 generic_file_write_iter+0x6c/0x168 mm/filemap.c:3932 call_write_iter include/linux/fs.h:2189 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x2dc/0x46c fs/read_write.c:584 ksys_write+0xb4/0x160 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x24/0x34 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x104 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&tree->tree_lock#2/1); lock(&HFS_I(tree->inode)->extents_lock); lock(&tree->tree_lock#2/1); lock(&HFS_I(tree->inode)->extents_lock); *** DEADLOCK *** 5 locks held by syz-executor.4/8910: #0: ffff0000c7adc8e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x12c/0x154 fs/file.c:1046 #1: ffff00011bff7460 (sb_writers#29){.+.+}-{0:0}, at: vfs_write+0x180/0x46c fs/read_write.c:580 #2: ffff0001221202a8 (&sb->s_type->i_mutex_key#36){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #2: ffff0001221202a8 (&sb->s_type->i_mutex_key#36){+.+.}-{3:3}, at: generic_file_write_iter+0x3c/0x168 mm/filemap.c:3929 #3: ffff0001221200f8 (&HFS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0x54/0x740 fs/hfs/extent.c:397 #4: ffff00011bff00b0 (&tree->tree_lock#2/1){+.+.}-{3:3}, at: hfs_find_init+0xac/0xcc stack backtrace: CPU: 0 PID: 8910 Comm: syz-executor.4 Not tainted 6.2.0-rc5-syzkaller-17295-g1dc22be1f91f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call trace: dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:163 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x2c4/0x2c8 kernel/locking/lockdep.c:2055 check_noncircular+0x14c/0x154 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055 lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668 __mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 hfs_extend_file+0x54/0x740 fs/hfs/extent.c:397 hfs_bmap_reserve+0x44/0xe8 fs/hfs/btree.c:234 __hfs_ext_write_extent+0xb8/0x138 fs/hfs/extent.c:121 __hfs_ext_cache_extent+0x58/0x1f0 fs/hfs/extent.c:174 hfs_ext_read_extent fs/hfs/extent.c:202 [inline] hfs_extend_file+0x14c/0x740 fs/hfs/extent.c:401 hfs_get_block+0x1c8/0x4c4 fs/hfs/extent.c:353 __block_write_begin_int+0x23c/0x9d4 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x74/0x14c fs/buffer.c:2102 cont_write_begin+0xf4/0x11c fs/buffer.c:2456 hfs_write_begin+0x64/0xac fs/hfs/inode.c:58 generic_perform_write+0xf0/0x2cc mm/filemap.c:3772 __generic_file_write_iter+0xd8/0x21c mm/filemap.c:3900 generic_file_write_iter+0x6c/0x168 mm/filemap.c:3932 call_write_iter include/linux/fs.h:2189 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x2dc/0x46c fs/read_write.c:584 ksys_write+0xb4/0x160 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x24/0x34 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x104 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584