F2FS-fs (loop5): Disable nat_bits due to incorrect cp_ver (9621037545273099749, 1067266233009637)
F2FS-fs (loop5): f2fs_check_nid_range: out-of-range nid=2, run fsck to fix.
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0 Not tainted
------------------------------------------------------
syz-executor.5/9232 is trying to acquire lock:
ffff88807761c088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_handle_error+0xf0/0x250

but task is already holding lock:
ffff88802a2f3130 (&nm_i->nat_tree_lock){++++}-{3:3}, at: f2fs_build_free_nids+0x71f/0x1190

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&nm_i->nat_tree_lock){++++}-{3:3}:
       lock_acquire+0x20b/0x600
       down_read+0x3d/0x50
       f2fs_get_node_info+0xf3/0x12d0
       __write_node_page+0x71f/0x27b0
       f2fs_sync_node_pages+0x104c/0x1690
       f2fs_write_checkpoint+0xe55/0x1ce0
       __checkpoint_and_complete_reqs+0xda/0x3b0
       issue_checkpoint_thread+0xda/0x250
       kthread+0x270/0x300
       ret_from_fork+0x1f/0x30

-> #3 (&sbi->node_change){++++}-{3:3}:
       lock_acquire+0x20b/0x600
       down_read+0x3d/0x50
       f2fs_vm_page_mkwrite+0x75c/0x1430
       do_page_mkwrite+0x1a1/0x600
       do_wp_page+0x506/0x3270
       handle_mm_fault+0x2388/0x51c0
       exc_page_fault+0x66a/0x880
       asm_exc_page_fault+0x26/0x30

-> #2 (mapping.invalidate_lock#6){++++}-{3:3}:
       lock_acquire+0x20b/0x600
       down_read+0x3d/0x50
       filemap_fault+0x617/0x17d0
       f2fs_filemap_fault+0x81/0x3d0
       __do_fault+0x136/0x500
       handle_mm_fault+0x32f3/0x51c0
       __get_user_pages+0x509/0x11e0
       populate_vma_page_range+0x21b/0x2b0
       __mm_populate+0x279/0x450
       vm_mmap_pgoff+0x212/0x2d0
       ksys_mmap_pgoff+0x4f9/0x6d0
       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
       f2fs_build_free_nids+0xca3/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

other info that might help us debug this:

Chain exists of:
  &sbi->sb_lock --> &sbi->node_change --> &nm_i->nat_tree_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&nm_i->nat_tree_lock);
                               lock(&sbi->node_change);
                               lock(&nm_i->nat_tree_lock);
  lock(&sbi->sb_lock);

 *** DEADLOCK ***

3 locks held by syz-executor.5/9232:
 #0: ffff888078a200e0 (&type->s_umount_key#51/1){+.+.}-{3:3}, at: alloc_super+0x217/0x930
 #1: ffff88802a2f32c8 (&nm_i->build_lock){+.+.}-{3:3}, at: f2fs_build_free_nids+0xcc/0x1190
 #2: ffff88802a2f3130 (&nm_i->nat_tree_lock){++++}-{3:3}, at: f2fs_build_free_nids+0x71f/0x1190

stack backtrace:
CPU: 1 PID: 9232 Comm: syz-executor.5 Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 <TASK>
 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
 f2fs_build_free_nids+0xca3/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
RIP: 0033:0x7f228ce8d5fa
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:00007f228dc1af88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00000000000105fc RCX: 00007f228ce8d5fa
RDX: 0000000020010600 RSI: 0000000020000000 RDI: 00007f228dc1afe0
RBP: 00007f228dc1b020 R08: 00007f228dc1b020 R09: 0000000000000816
R10: 0000000000000816 R11: 0000000000000202 R12: 0000000020010600
R13: 0000000020000000 R14: 00007f228dc1afe0 R15: 0000000020000080
 </TASK>