======================================================
WARNING: possible circular locking dependency detected
6.4.0-rc7-next-20230622-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.3/18492 is trying to acquire lock:
ffff88808b080990 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:771 [inline]
ffff88808b080990 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: f2fs_file_mmap+0x154/0x290 fs/f2fs/file.c:527
but task is already holding lock:
ffff88807b6e27a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:110 [inline]
ffff88807b6e27a0 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x158/0x3b0 mm/util.c:541
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&mm->mmap_lock){++++}-{3:3}:
internal_get_user_pages_fast+0x13c0/0x3370 mm/gup.c:3122
pin_user_pages_fast+0xa8/0xf0 mm/gup.c:3246
iov_iter_extract_user_pages lib/iov_iter.c:1768 [inline]
iov_iter_extract_pages+0x293/0x18f0 lib/iov_iter.c:1831
__bio_iov_iter_get_pages block/bio.c:1276 [inline]
bio_iov_iter_get_pages block/bio.c:1349 [inline]
bio_iov_iter_get_pages+0x33b/0xd50 block/bio.c:1336
iomap_dio_bio_iter+0x82a/0x1430 fs/iomap/direct-io.c:317
iomap_dio_iter fs/iomap/direct-io.c:430 [inline]
__iomap_dio_rw+0x1010/0x1d80 fs/iomap/direct-io.c:575
f2fs_dio_write_iter fs/f2fs/file.c:4657 [inline]
f2fs_file_write_iter+0x121b/0x2500 fs/f2fs/file.c:4766
call_write_iter include/linux/fs.h:1871 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x981/0xda0 fs/read_write.c:584
ksys_write+0x122/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #1 (&fi->i_gc_rwsem[WRITE]){.+.+}-{3:3}:
down_read+0x9c/0x480 kernel/locking/rwsem.c:1520
f2fs_down_read fs/f2fs/f2fs.h:2107 [inline]
f2fs_dio_write_iter fs/f2fs/file.c:4643 [inline]
f2fs_file_write_iter+0x1161/0x2500 fs/f2fs/file.c:4766
call_write_iter include/linux/fs.h:1871 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x981/0xda0 fs/read_write.c:584
ksys_write+0x122/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3142 [inline]
check_prevs_add kernel/locking/lockdep.c:3261 [inline]
validate_chain kernel/locking/lockdep.c:3876 [inline]
__lock_acquire+0x2e9d/0x5e20 kernel/locking/lockdep.c:5144
lock_acquire.part.0+0x11c/0x370 kernel/locking/lockdep.c:5761
down_write+0x92/0x200 kernel/locking/rwsem.c:1573
inode_lock include/linux/fs.h:771 [inline]
f2fs_file_mmap+0x154/0x290 fs/f2fs/file.c:527
call_mmap include/linux/fs.h:1876 [inline]
mmap_region+0x6cf/0x2570 mm/mmap.c:2669
do_mmap+0x837/0xea0 mm/mmap.c:1373
vm_mmap_pgoff+0x1a4/0x3b0 mm/util.c:543
ksys_mmap_pgoff+0x42b/0x5b0 mm/mmap.c:1419
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/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:
&sb->s_type->i_mutex_key#28 --> &fi->i_gc_rwsem[WRITE] --> &mm->mmap_lock
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_lock);
lock(&fi->i_gc_rwsem[WRITE]);
lock(&mm->mmap_lock);
lock(&sb->s_type->i_mutex_key#28);
*** DEADLOCK ***
1 lock held by syz-executor.3/18492:
#0: ffff88807b6e27a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:110 [inline]
#0: ffff88807b6e27a0 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x158/0x3b0 mm/util.c:541
stack backtrace:
CPU: 0 PID: 18492 Comm: syz-executor.3 Not tainted 6.4.0-rc7-next-20230622-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
check_noncircular+0x2df/0x3b0 kernel/locking/lockdep.c:2195
check_prev_add kernel/locking/lockdep.c:3142 [inline]
check_prevs_add kernel/locking/lockdep.c:3261 [inline]
validate_chain kernel/locking/lockdep.c:3876 [inline]
__lock_acquire+0x2e9d/0x5e20 kernel/locking/lockdep.c:5144
lock_acquire.part.0+0x11c/0x370 kernel/locking/lockdep.c:5761
down_write+0x92/0x200 kernel/locking/rwsem.c:1573
inode_lock include/linux/fs.h:771 [inline]
f2fs_file_mmap+0x154/0x290 fs/f2fs/file.c:527
call_mmap include/linux/fs.h:1876 [inline]
mmap_region+0x6cf/0x2570 mm/mmap.c:2669
do_mmap+0x837/0xea0 mm/mmap.c:1373
vm_mmap_pgoff+0x1a4/0x3b0 mm/util.c:543
ksys_mmap_pgoff+0x42b/0x5b0 mm/mmap.c:1419
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f8368a8c389
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:00007f8369770168 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f8368babf80 RCX: 00007f8368a8c389
RDX: 00000000027fffff RSI: 0000000000600000 RDI: 0000000020000000
RBP: 00007f8368ad7493 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000004002011 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff81bef73f R14: 00007f8369770300 R15: 0000000000022000
</TASK>