F2FS-fs (loop4): Mounted with checkpoint version = 48b305e5
F2FS-fs (loop4): f2fs_check_nid_range: out-of-range nid=1, run fsck to fix.
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0 Not tainted
------------------------------------------------------
syz-executor.4/13125 is trying to acquire lock:
ffff888017db8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_handle_error+0xf0/0x250

but task is already holding lock:
ffff888020f37130 (&nm_i->nat_tree_lock){++++}-{3:3}, at: f2fs_build_free_nids+0x316/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
       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_creat+0x123/0x160
       do_syscall_64+0x41/0xc0
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #3 (&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_creat+0x123/0x160
       do_syscall_64+0x41/0xc0
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (mapping.invalidate_lock#7){++++}-{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+0x505/0x1190
       f2fs_alloc_nid+0x221/0x740
       f2fs_new_inode+0x119/0x1090
       f2fs_mkdir+0x127/0x530
       vfs_mkdir+0x3ba/0x590
       do_mkdirat+0x237/0x4f0
       __x64_sys_mkdirat+0x89/0xa0
       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->cp_rwsem --> &nm_i->nat_tree_lock

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

4 locks held by syz-executor.4/13125:
 #0: ffff8880279dc460 (sb_writers#21){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90
 #1: ffff888072b49c20 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: filename_create+0x249/0x500
 #2: ffff888020f372c8 (&nm_i->build_lock){+.+.}-{3:3}, at: f2fs_build_free_nids+0xcc/0x1190
 #3: ffff888020f37130 (&nm_i->nat_tree_lock){++++}-{3:3}, at: f2fs_build_free_nids+0x316/0x1190

stack backtrace:
CPU: 0 PID: 13125 Comm: syz-executor.4 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+0x505/0x1190
 f2fs_alloc_nid+0x221/0x740
 f2fs_new_inode+0x119/0x1090
 f2fs_mkdir+0x127/0x530
 vfs_mkdir+0x3ba/0x590
 do_mkdirat+0x237/0x4f0
 __x64_sys_mkdirat+0x89/0xa0
 do_syscall_64+0x41/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f618a88c0c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f61893fe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f618a9abf80 RCX: 00007f618a88c0c9
RDX: 0000000000000000 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f618a8e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff4030ff6f R14: 00007f61893fe300 R15: 0000000000022000
 </TASK>
F2FS-fs (loop4): f2fs_check_nid_range: out-of-range nid=2, run fsck to fix.