======================================================
WARNING: possible circular locking dependency detected
6.13.0-rc2-syzkaller-00192-g243f750a2df0 #0 Not tainted
------------------------------------------------------
syz.9.298/9068 is trying to acquire lock:
ffff8880535f60e0 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x246/0x29c0 mm/gup.c:3416
but task is already holding lock:
ffff888078be0398 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:838 [inline]
ffff888078be0398 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: ntfs_file_write_iter+0x291/0x7a0 fs/ntfs3/file.c:1240
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}:
lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
down_write+0x99/0x220 kernel/locking/rwsem.c:1577
inode_lock include/linux/fs.h:818 [inline]
ntfs_file_mmap+0x5bc/0x850 fs/ntfs3/file.c:379
call_mmap include/linux/fs.h:2183 [inline]
mmap_file mm/internal.h:124 [inline]
__mmap_new_file_vma mm/vma.c:2291 [inline]
__mmap_new_vma mm/vma.c:2355 [inline]
__mmap_region+0x2204/0x2cd0 mm/vma.c:2456
mmap_region+0x226/0x2c0 mm/mmap.c:1348
do_mmap+0x8f0/0x1000 mm/mmap.c:496
vm_mmap_pgoff+0x1dd/0x3d0 mm/util.c:580
ksys_mmap_pgoff+0x4eb/0x720 mm/mmap.c:542
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
-> #0 (&mm->mmap_lock){++++}-{4:4}:
check_prev_add kernel/locking/lockdep.c:3161 [inline]
check_prevs_add kernel/locking/lockdep.c:3280 [inline]
validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
__lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
gup_fast_fallback+0x25f/0x29c0 mm/gup.c:3416
pin_user_pages_fast+0xcc/0x160 mm/gup.c:3540
iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline]
iov_iter_extract_pages+0x3bb/0x5c0 lib/iov_iter.c:1907
dio_refill_pages fs/direct-io.c:172 [inline]
dio_get_page fs/direct-io.c:213 [inline]
do_direct_IO fs/direct-io.c:915 [inline]
__blockdev_direct_IO+0x1443/0x4890 fs/direct-io.c:1243
blockdev_direct_IO include/linux/fs.h:3313 [inline]
ntfs_direct_IO+0x194/0x370 fs/ntfs3/inode.c:806
generic_file_direct_write+0x1e6/0x400 mm/filemap.c:3978
__generic_file_write_iter+0x126/0x230 mm/filemap.c:4142
ntfs_file_write_iter+0x69c/0x7a0 fs/ntfs3/file.c:1267
new_sync_write fs/read_write.c:586 [inline]
vfs_write+0xaeb/0xd30 fs/read_write.c:679
ksys_write+0x18f/0x2b0 fs/read_write.c:731
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&sb->s_type->i_mutex_key#29);
lock(&mm->mmap_lock);
lock(&sb->s_type->i_mutex_key#29);
rlock(&mm->mmap_lock);
*** DEADLOCK ***
3 locks held by syz.9.298/9068:
#0: ffff88802d7ad0b8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x254/0x320 fs/file.c:1191
#1: ffff88805260c420 (sb_writers#20){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2964 [inline]
#1: ffff88805260c420 (sb_writers#20){.+.+}-{0:0}, at: vfs_write+0x225/0xd30 fs/read_write.c:675
#2: ffff888078be0398 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:838 [inline]
#2: ffff888078be0398 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: ntfs_file_write_iter+0x291/0x7a0 fs/ntfs3/file.c:1240
stack backtrace:
CPU: 1 UID: 0 PID: 9068 Comm: syz.9.298 Not tainted 6.13.0-rc2-syzkaller-00192-g243f750a2df0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Call Trace:
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
check_prev_add kernel/locking/lockdep.c:3161 [inline]
check_prevs_add kernel/locking/lockdep.c:3280 [inline]
validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
__lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
gup_fast_fallback+0x25f/0x29c0 mm/gup.c:3416
pin_user_pages_fast+0xcc/0x160 mm/gup.c:3540
iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline]
iov_iter_extract_pages+0x3bb/0x5c0 lib/iov_iter.c:1907
dio_refill_pages fs/direct-io.c:172 [inline]
dio_get_page fs/direct-io.c:213 [inline]
do_direct_IO fs/direct-io.c:915 [inline]
__blockdev_direct_IO+0x1443/0x4890 fs/direct-io.c:1243
blockdev_direct_IO include/linux/fs.h:3313 [inline]
ntfs_direct_IO+0x194/0x370 fs/ntfs3/inode.c:806
generic_file_direct_write+0x1e6/0x400 mm/filemap.c:3978
__generic_file_write_iter+0x126/0x230 mm/filemap.c:4142
ntfs_file_write_iter+0x69c/0x7a0 fs/ntfs3/file.c:1267
new_sync_write fs/read_write.c:586 [inline]
vfs_write+0xaeb/0xd30 fs/read_write.c:679
ksys_write+0x18f/0x2b0 fs/read_write.c:731
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe451f85d19
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe452d7d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fe452176160 RCX: 00007fe451f85d19
RDX: 0000000000000200 RSI: 0000000020000600 RDI: 000000000000000a
RBP: 00007fe452001a20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fe452176160 R15: 00007fff0318d8f8
Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
File: /2/w5T )`)YFnA@T<3ڂ$rcnHwC" -8/file1 PID: 9068 Comm: syz.9.298
Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
File: /2/w5T )`)YFnA@T<3ڂ$rcnHwC" -8/file1 PID: 9068 Comm: syz.9.298