loop3: detected capacity change from 0 to 40427 F2FS-fs (loop3): Mismatch valid blocks 4 vs. 6 ====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc7-syzkaller-00018-g0983f6bf2bfc #0 Not tainted ------------------------------------------------------ syz-executor.3/32762 is trying to acquire lock: ffff88807e5d4088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_handle_error+0xf0/0x250 but task is already holding lock: ffff88807187c3b8 (&array[i].journal_rwsem){++++}-{3:3}, at: build_sit_entries+0xfcd/0x1de0 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #6 (&array[i].journal_rwsem){++++}-{3:3}: lock_acquire+0x20b/0x600 down_read+0x3d/0x50 scan_curseg_cache+0xa6/0x410 f2fs_build_free_nids+0xf04/0x1190 f2fs_fill_super+0x46f3/0x6f30 mount_bdev+0x271/0x3a0 legacy_get_tree+0xef/0x190 vfs_get_tree+0x8c/0x270 do_new_mount+0x28f/0xae0 __se_sys_mount+0x2c9/0x3b0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #5 (&nm_i->nat_tree_lock){++++}-{3:3}: lock_acquire+0x20b/0x600 down_read+0x3d/0x50 f2fs_get_node_info+0xf3/0x12d0 f2fs_new_node_page+0x260/0xb40 f2fs_get_dnode_of_data+0x6f9/0x1e00 f2fs_reserve_block+0x54/0x250 f2fs_get_new_data_page+0x1b0/0x7c0 f2fs_add_regular_entry+0x642/0xe50 f2fs_do_add_link+0x2fb/0x500 f2fs_create+0x32c/0x530 path_openat+0x12b9/0x2e30 do_filp_open+0x26d/0x500 do_sys_openat2+0x128/0x4f0 __x64_sys_open+0x225/0x270 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #4 (&sbi->cp_rwsem){++++}-{3:3}: lock_acquire+0x20b/0x600 down_read+0x3d/0x50 f2fs_do_truncate_blocks+0x228/0xf60 f2fs_truncate_blocks+0x10d/0x2f0 f2fs_truncate+0x4b6/0x8b0 f2fs_setattr+0xb59/0x1110 notify_change+0xdd1/0x1080 do_truncate+0x207/0x2f0 path_openat+0x278f/0x2e30 do_filp_open+0x26d/0x500 do_sys_openat2+0x128/0x4f0 __x64_sys_openat+0x247/0x290 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #3 (mapping.invalidate_lock#3){++++}-{3:3}: lock_acquire+0x20b/0x600 down_read+0x3d/0x50 f2fs_vm_page_mkwrite+0x536/0x1430 do_page_mkwrite+0x1a1/0x600 handle_mm_fault+0x2156/0x51c0 exc_page_fault+0x66a/0x880 asm_exc_page_fault+0x26/0x30 copy_user_enhanced_fast_string+0xe/0x40 _copy_to_iter+0x2f5/0x1040 copy_page_to_iter+0xe7/0x1d0 filemap_read+0x27f7/0x32d0 f2fs_file_read_iter+0x139/0xf20 vfs_read+0x7cb/0xc20 ksys_read+0x17c/0x2a0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #2 (sb_pagefaults#3){.+.+}-{0:0}: lock_acquire+0x20b/0x600 __sb_start_write+0x58/0x1a0 f2fs_vm_page_mkwrite+0x468/0x1430 do_page_mkwrite+0x1a1/0x600 handle_mm_fault+0x2156/0x51c0 exc_page_fault+0x66a/0x880 asm_exc_page_fault+0x26/0x30 copy_user_enhanced_fast_string+0xe/0x40 _copy_to_iter+0x2f5/0x1040 copy_page_to_iter+0xe7/0x1d0 filemap_read+0x27f7/0x32d0 f2fs_file_read_iter+0x139/0xf20 vfs_read+0x7cb/0xc20 ksys_read+0x17c/0x2a0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&mm->mmap_lock){++++}-{3:3}: lock_acquire+0x20b/0x600 __might_fault+0xba/0x120 _copy_to_user+0x2a/0x130 __f2fs_ioctl+0xaccd/0xb2b0 __se_sys_ioctl+0xf1/0x160 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sbi->sb_lock){++++}-{3:3}: validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x20b/0x600 down_write+0x3a/0x60 f2fs_handle_error+0xf0/0x250 check_block_count+0x35b/0x490 build_sit_entries+0x11d6/0x1de0 f2fs_build_segment_manager+0x201f/0x31d0 f2fs_fill_super+0x46b9/0x6f30 mount_bdev+0x271/0x3a0 legacy_get_tree+0xef/0x190 vfs_get_tree+0x8c/0x270 do_new_mount+0x28f/0xae0 __se_sys_mount+0x2c9/0x3b0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &sbi->sb_lock --> &nm_i->nat_tree_lock --> &array[i].journal_rwsem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&array[i].journal_rwsem); lock(&nm_i->nat_tree_lock); lock(&array[i].journal_rwsem); lock(&sbi->sb_lock); *** DEADLOCK *** 2 locks held by syz-executor.3/32762: #0: ffff88807cbc40e0 (&type->s_umount_key#74/1){+.+.}-{3:3}, at: alloc_super+0x217/0x930 #1: ffff88807187c3b8 (&array[i].journal_rwsem){++++}-{3:3}, at: build_sit_entries+0xfcd/0x1de0 stack backtrace: CPU: 0 PID: 32762 Comm: syz-executor.3 Not tainted 6.2.0-rc7-syzkaller-00018-g0983f6bf2bfc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 Call Trace: dump_stack_lvl+0x1b5/0x2a0 check_noncircular+0x2d1/0x390 validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x20b/0x600 down_write+0x3a/0x60 f2fs_handle_error+0xf0/0x250 check_block_count+0x35b/0x490 build_sit_entries+0x11d6/0x1de0 f2fs_build_segment_manager+0x201f/0x31d0 f2fs_fill_super+0x46b9/0x6f30 mount_bdev+0x271/0x3a0 legacy_get_tree+0xef/0x190 vfs_get_tree+0x8c/0x270 do_new_mount+0x28f/0xae0 __se_sys_mount+0x2c9/0x3b0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f521e28d62a Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f521f048f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00000000000054f1 RCX: 00007f521e28d62a RDX: 0000000020000040 RSI: 0000000020000080 RDI: 00007f521f048fe0 RBP: 00007f521f049020 R08: 00007f521f049020 R09: 0000000000000003 R10: 0000000000000003 R11: 0000000000000202 R12: 0000000020000040 R13: 0000000020000080 R14: 00007f521f048fe0 R15: 00000000200000c0 F2FS-fs (loop3): Failed to initialize F2FS segment manager (-117)