loop1: detected capacity change from 0 to 40427 F2FS-fs (loop1): Mismatch valid blocks 4 vs. 6 ====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc6-syzkaller-00083-ge7368fd30165 #0 Not tainted ------------------------------------------------------ syz-executor.1/23448 is trying to acquire lock: ffff888027cc8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] ffff888027cc8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_handle_error+0xe0/0x230 fs/f2fs/super.c:3926 but task is already holding lock: ffff88801dff43b8 (&array[i].journal_rwsem){++++}-{3:3}, at: build_sit_entries+0xff9/0x1e40 fs/f2fs/segment.c:4450 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (&array[i].journal_rwsem){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 scan_curseg_cache+0xa6/0x420 fs/f2fs/node.c:2404 __f2fs_build_free_nids fs/f2fs/node.c:2516 [inline] f2fs_build_free_nids+0xf07/0x1190 fs/f2fs/node.c:2531 f2fs_fill_super+0x4a5f/0x6ee0 fs/f2fs/super.c:4334 mount_bdev+0x26c/0x3a0 fs/super.c:1359 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1489 do_new_mount+0x289/0xad0 fs/namespace.c:3145 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3674 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #3 (&nm_i->nat_tree_lock){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 f2fs_down_read fs/f2fs/f2fs.h:2188 [inline] f2fs_get_node_info+0x100/0x1720 fs/f2fs/node.c:564 f2fs_do_write_data_page+0xf87/0x2570 fs/f2fs/data.c:2728 f2fs_write_single_data_page+0x1162/0x1c90 fs/f2fs/data.c:2863 f2fs_write_cache_pages+0xf6e/0x2330 fs/f2fs/data.c:3115 __f2fs_write_data_pages fs/f2fs/data.c:3265 [inline] f2fs_write_data_pages+0x7d2/0xc30 fs/f2fs/data.c:3292 do_writepages+0x3c3/0x680 mm/page-writeback.c:2581 filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388 __filemap_fdatawrite_range mm/filemap.c:421 [inline] filemap_write_and_wait_range+0x1df/0x2e0 mm/filemap.c:674 f2fs_insert_range+0x37c/0x3c0 fs/f2fs/file.c:1678 f2fs_fallocate+0x4bd/0x6e0 fs/f2fs/file.c:1841 vfs_fallocate+0x515/0x670 fs/open.c:323 ksys_fallocate fs/open.c:346 [inline] __do_sys_fallocate fs/open.c:354 [inline] __se_sys_fallocate fs/open.c:352 [inline] __x64_sys_fallocate+0xb9/0x100 fs/open.c:352 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #2 (mapping.invalidate_lock#3){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 filemap_invalidate_lock_shared include/linux/fs.h:811 [inline] filemap_fault+0x2fb/0x1060 mm/filemap.c:3146 f2fs_filemap_fault+0x75/0xb0 fs/f2fs/file.c:44 __do_fault+0x136/0x4f0 mm/memory.c:4163 do_read_fault mm/memory.c:4514 [inline] do_fault mm/memory.c:4643 [inline] handle_pte_fault mm/memory.c:4931 [inline] __handle_mm_fault mm/memory.c:5073 [inline] handle_mm_fault+0x2066/0x26b0 mm/memory.c:5219 faultin_page mm/gup.c:926 [inline] __get_user_pages+0x52b/0x1270 mm/gup.c:1153 populate_vma_page_range+0x216/0x2b0 mm/gup.c:1526 __mm_populate+0x2ad/0x460 mm/gup.c:1640 mm_populate include/linux/mm.h:2874 [inline] vm_mmap_pgoff+0x200/0x2b0 mm/util.c:525 ksys_mmap_pgoff+0x48c/0x6d0 mm/mmap.c:1457 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&mm->mmap_lock){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __might_fault+0xb2/0x110 mm/memory.c:5647 _copy_to_user+0x26/0x130 lib/usercopy.c:29 copy_to_user include/linux/uaccess.h:169 [inline] f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2365 [inline] __f2fs_ioctl+0xaf72/0xb540 fs/f2fs/file.c:4169 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sbi->sb_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write+0x9c/0x270 kernel/locking/rwsem.c:1562 f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] f2fs_handle_error+0xe0/0x230 fs/f2fs/super.c:3926 check_block_count+0x35d/0x490 build_sit_entries+0x1216/0x1e40 fs/f2fs/segment.c:4470 f2fs_build_segment_manager+0x1c2d/0x2a70 fs/f2fs/segment.c:5159 f2fs_fill_super+0x4a23/0x6ee0 fs/f2fs/super.c:4328 mount_bdev+0x26c/0x3a0 fs/super.c:1359 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1489 do_new_mount+0x289/0xad0 fs/namespace.c:3145 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3674 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 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.1/23448: #0: ffff88802995a0e0 (&type->s_umount_key#49/1){+.+.}-{3:3}, at: alloc_super+0x212/0x920 fs/super.c:228 #1: ffff88801dff43b8 (&array[i].journal_rwsem){++++}-{3:3}, at: build_sit_entries+0xff9/0x1e40 fs/f2fs/segment.c:4450 stack backtrace: CPU: 0 PID: 23448 Comm: syz-executor.1 Not tainted 6.2.0-rc6-syzkaller-00083-ge7368fd30165 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 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+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write+0x9c/0x270 kernel/locking/rwsem.c:1562 f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] f2fs_handle_error+0xe0/0x230 fs/f2fs/super.c:3926 check_block_count+0x35d/0x490 build_sit_entries+0x1216/0x1e40 fs/f2fs/segment.c:4470 f2fs_build_segment_manager+0x1c2d/0x2a70 fs/f2fs/segment.c:5159 f2fs_fill_super+0x4a23/0x6ee0 fs/f2fs/super.c:4328 mount_bdev+0x26c/0x3a0 fs/super.c:1359 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1489 do_new_mount+0x289/0xad0 fs/namespace.c:3145 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3674 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f50e748d5fa 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:00007f50e816af88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00000000000054f1 RCX: 00007f50e748d5fa RDX: 0000000020000040 RSI: 0000000020000080 RDI: 00007f50e816afe0 RBP: 00007f50e816b020 R08: 00007f50e816b020 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000040 R13: 0000000020000080 R14: 00007f50e816afe0 R15: 00000000200000c0 F2FS-fs (loop1): Failed to initialize F2FS segment manager (-117)