======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc7-syzkaller-00011-g05ecb680708a #0 Not tainted
------------------------------------------------------
syz-executor.0/13596 is trying to acquire lock:
ffff888073504a70 (mapping.invalidate_lock#3){++++}-{3:3}, at: f2fs_vm_page_mkwrite+0x536/0x1430

but task is already holding lock:
ffff888040dce558 (sb_pagefaults#6){.+.+}-{0:0}, at: f2fs_vm_page_mkwrite+0x468/0x1430

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (sb_pagefaults#6){.+.+}-{0:0}:
       lock_acquire+0x20b/0x600
       __sb_start_write+0x58/0x1a0
       f2fs_vm_page_mkwrite+0x468/0x1430
       do_page_mkwrite+0x1a1/0x600
       handle_mm_fault+0x2156/0x51c0
       exc_page_fault+0x66a/0x880
       asm_exc_page_fault+0x26/0x30

-> #3 (&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

-> #2 (&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

-> #1 (&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

-> #0 (mapping.invalidate_lock#3){++++}-{3:3}:
       validate_chain+0x166b/0x5860
       __lock_acquire+0x125b/0x1f80
       lock_acquire+0x20b/0x600
       down_read+0x3d/0x50
       f2fs_vm_page_mkwrite+0x536/0x1430
       do_page_mkwrite+0x1a1/0x600
       handle_mm_fault+0x2156/0x51c0
       exc_page_fault+0x66a/0x880
       asm_exc_page_fault+0x26/0x30

other info that might help us debug this:

Chain exists of:
  mapping.invalidate_lock#3 --> &mm->mmap_lock --> sb_pagefaults#6

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(sb_pagefaults#6);
                               lock(&mm->mmap_lock);
                               lock(sb_pagefaults#6);
  lock(mapping.invalidate_lock#3);

 *** DEADLOCK ***

2 locks held by syz-executor.0/13596:
 #0: ffff88807de3be98 (&mm->mmap_lock){++++}-{3:3}, at: exc_page_fault+0x546/0x880
 #1: ffff888040dce558 (sb_pagefaults#6){.+.+}-{0:0}, at: f2fs_vm_page_mkwrite+0x468/0x1430

stack backtrace:
CPU: 0 PID: 13596 Comm: syz-executor.0 Not tainted 6.2.0-rc7-syzkaller-00011-g05ecb680708a #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_read+0x3d/0x50
 f2fs_vm_page_mkwrite+0x536/0x1430
 do_page_mkwrite+0x1a1/0x600
 handle_mm_fault+0x2156/0x51c0
 exc_page_fault+0x66a/0x880
 asm_exc_page_fault+0x26/0x30
RIP: 0033:0x7fe263c2be3a
Code: 30 48 8b 34 24 48 85 f6 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fe 01 0f 85 a1 01 00 00 48 8b 44 24 10 8b 74 24 18 <89> 30 e9 d2 fc ff ff 48 8b 44 24 10 8b 10 48 8b 04 24 48 85 c0 0f
RSP: 002b:00007fff4f9eb7f0 EFLAGS: 00010246
RAX: 0000000020008000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: f1087e9dae49524f RSI: 00000000ffffffff RDI: 0000555556c092e8
RBP: 00007fff4f9eb8e8 R08: 0000000000000000 R09: 0000000000000000
R10: 00007fe263808258 R11: 0000000000000246 R12: 0000000000085c6e
R13: 00007fff4f9eb910 R14: 00007fe263dabf80 R15: 0000000000000032
 </TASK>