KCSAN: data-race in next_uptodate_page / simple_write_end (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 22da5264abf4 Merge tag '5.18-rc3-ksmbd-fixes' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1599cadcf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=30f43a6ded7cebcd
dashboard link: https://syzkaller.appspot.com/bug?extid=bac38a023cc33a71abc3
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bac38a...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in next_uptodate_page / simple_write_end

write to 0xffff888136937620 of 8 bytes by task 3174 on cpu 0:
i_size_write include/linux/fs.h:878 [inline]
simple_write_end+0x11e/0x2f0 fs/libfs.c:618
generic_perform_write+0x26a/0x3f0 mm/filemap.c:3798
__generic_file_write_iter+0xe3/0x280 mm/filemap.c:3915
generic_file_write_iter+0x75/0x130 mm/filemap.c:3947
call_write_iter include/linux/fs.h:2050 [inline]
new_sync_write fs/read_write.c:504 [inline]
vfs_write+0x71c/0x890 fs/read_write.c:591
ksys_write+0xe8/0x1a0 fs/read_write.c:644
__do_sys_write fs/read_write.c:656 [inline]
__se_sys_write fs/read_write.c:653 [inline]
__x64_sys_write+0x3e/0x50 fs/read_write.c:653
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888136937620 of 8 bytes by task 3202 on cpu 1:
i_size_read include/linux/fs.h:856 [inline]
next_uptodate_page+0x26f/0x4e0 mm/filemap.c:3311
next_map_page mm/filemap.c:3336 [inline]
filemap_map_pages+0x9d1/0xae0 mm/filemap.c:3403
do_fault_around mm/memory.c:4219 [inline]
do_read_fault mm/memory.c:4234 [inline]
do_fault+0x433/0xb20 mm/memory.c:4369
handle_pte_fault mm/memory.c:4627 [inline]
__handle_mm_fault mm/memory.c:4763 [inline]
handle_mm_fault+0x825/0xa40 mm/memory.c:4861
faultin_page mm/gup.c:878 [inline]
__get_user_pages+0x306/0xb80 mm/gup.c:1099
populate_vma_page_range mm/gup.c:1442 [inline]
__mm_populate+0x26e/0x3a0 mm/gup.c:1555
mm_populate include/linux/mm.h:2701 [inline]
vm_mmap_pgoff+0x160/0x1f0 mm/util.c:524
ksys_mmap_pgoff+0x265/0x320 mm/mmap.c:1628
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x0000000000f23000 -> 0x0000000000f25000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3202 Comm: syz-executor.4 Not tainted 5.18.0-rc3-syzkaller-00235-g22da5264abf4-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.