loop2: detected capacity change from 0 to 40427 F2FS-fs (loop2): Wrong journal entry on segno 458752 ====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc4-syzkaller-00077-gd368967cb103 #0 Not tainted ------------------------------------------------------ syz-executor.2/17649 is trying to acquire lock: ffff88807e6d8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] ffff88807e6d8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_handle_error+0xe0/0x230 fs/f2fs/super.c:3926 but task is already holding lock: ffff8880754ac3b8 (&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: -> #5 (&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 -> #4 (&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 __write_node_page+0x7a5/0x20a0 fs/f2fs/node.c:1616 f2fs_sync_node_pages+0x124d/0x1a80 fs/f2fs/node.c:2020 block_operations fs/f2fs/checkpoint.c:1275 [inline] f2fs_write_checkpoint+0xeae/0x1d60 fs/f2fs/checkpoint.c:1655 __write_checkpoint_sync fs/f2fs/checkpoint.c:1772 [inline] __checkpoint_and_complete_reqs+0xd1/0x3a0 fs/f2fs/checkpoint.c:1791 issue_checkpoint_thread+0xdc/0x280 fs/f2fs/checkpoint.c:1822 kthread+0x266/0x300 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 -> #3 (&sbi->node_change){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_read+0x39/0x50 kernel/locking/rwsem.c:1509 f2fs_vm_page_mkwrite+0x6cb/0x1350 fs/f2fs/file.c:116 do_page_mkwrite+0x19e/0x5e0 mm/memory.c:2947 do_shared_fault mm/memory.c:4579 [inline] do_fault mm/memory.c:4647 [inline] handle_pte_fault mm/memory.c:4931 [inline] __handle_mm_fault mm/memory.c:5073 [inline] handle_mm_fault+0x1952/0x26b0 mm/memory.c:5219 do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428 handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 -> #2 (mapping.invalidate_lock#4){++++}-{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_shared_fault mm/memory.c:4569 [inline] do_fault mm/memory.c:4647 [inline] handle_pte_fault mm/memory.c:4931 [inline] __handle_mm_fault mm/memory.c:5073 [inline] handle_mm_fault+0x18bc/0x26b0 mm/memory.c:5219 do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428 handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 -> #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 build_sit_entries+0x1bdc/0x1e40 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.2/17649: #0: ffff8880788e40e0 (&type->s_umount_key#64/1){+.+.}-{3:3}, at: alloc_super+0x212/0x920 fs/super.c:228 #1: ffff8880754ac3b8 (&array[i].journal_rwsem){++++}-{3:3}, at: build_sit_entries+0xff9/0x1e40 fs/f2fs/segment.c:4450 stack backtrace: CPU: 1 PID: 17649 Comm: syz-executor.2 Not tainted 6.2.0-rc4-syzkaller-00077-gd368967cb103 #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 build_sit_entries+0x1bdc/0x1e40 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:0x7fac6b88d5fa 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:00007fac6c610f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00000000000054ea RCX: 00007fac6b88d5fa RDX: 0000000020000040 RSI: 0000000020000080 RDI: 00007fac6c610fe0 RBP: 00007fac6c611020 R08: 00007fac6c611020 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000040 R13: 0000000020000080 R14: 00007fac6c610fe0 R15: 0000000020000480 F2FS-fs (loop2): Failed to initialize F2FS segment manager (-117)