======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc7-syzkaller-00013-g513c1a3d3f19 #0 Not tainted
------------------------------------------------------
syz-executor.4/28275 is trying to acquire lock:
ffff88807c143e98 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x93/0x120

but task is already holding lock:
ffff888018dbc088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x350c/0xb2b0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&sbi->sb_lock){++++}-{3:3}:
       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

-> #2 (&nm_i->nat_tree_lock){++++}-{3:3}:
       lock_acquire+0x20b/0x600
       down_read+0x3d/0x50
       f2fs_get_node_info+0xf3/0x12d0
       f2fs_do_write_data_page+0x10a8/0x27c0
       f2fs_write_single_data_page+0x14c1/0x2140
       f2fs_write_data_pages+0x1948/0x2ed0
       do_writepages+0x3a6/0x660
       filemap_fdatawrite_wbc+0x125/0x180
       filemap_write_and_wait_range+0x1e5/0x2e0
       f2fs_collapse_range+0x314/0x3b0
       f2fs_fallocate+0x46f/0x6d0
       vfs_fallocate+0x54b/0x6b0
       __x64_sys_fallocate+0xbd/0x100
       do_syscall_64+0x41/0xc0
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (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+0x20ae/0x51c0
       exc_page_fault+0x66a/0x880
       asm_exc_page_fault+0x26/0x30

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       validate_chain+0x166b/0x5860
       __lock_acquire+0x125b/0x1f80
       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

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &nm_i->nat_tree_lock --> &sbi->sb_lock

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz-executor.4/28275:
 #0: ffff88801e12a460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write_file+0x5e/0x1f0
 #1: ffff888018dbc088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x350c/0xb2b0

stack backtrace:
CPU: 0 PID: 28275 Comm: syz-executor.4 Not tainted 6.2.0-rc7-syzkaller-00013-g513c1a3d3f19 #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
 __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
RIP: 0033:0x7f2f3c88c0f9
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:00007f2f3d5a8168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2f3c9abf80 RCX: 00007f2f3c88c0f9
RDX: 0020000000000000 RSI: 0000000040106614 RDI: 0000000000000005
RBP: 00007f2f3c8e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffaa22b4df R14: 00007f2f3d5a8300 R15: 0000000000022000
 </TASK>