KCSAN: data-race in copy_page_from_iter / copy_page_from_iter (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b9b4c79e5830 Merge tag 'sound-5.18-rc3' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146129e0f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8fc0fa8e947beef
dashboard link: https://syzkaller.appspot.com/bug?extid=d5a1860863290774d676
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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+d5a186...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in copy_page_from_iter / copy_page_from_iter

write to 0xffff888126add000 of 4096 bytes by task 22907 on cpu 0:
instrument_copy_from_user include/linux/instrumented.h:136 [inline]
copyin lib/iov_iter.c:165 [inline]
copy_page_from_iter_iovec lib/iov_iter.c:310 [inline]
copy_page_from_iter+0x279/0x5f0 lib/iov_iter.c:902
process_vm_rw_pages mm/process_vm_access.c:43 [inline]
process_vm_rw_single_vec+0x273/0x440 mm/process_vm_access.c:117
process_vm_rw_core mm/process_vm_access.c:215 [inline]
process_vm_rw+0x3e1/0x570 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0x76/0x90 mm/process_vm_access.c:298
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

write to 0xffff888126add000 of 4096 bytes by task 22906 on cpu 1:
instrument_copy_from_user include/linux/instrumented.h:136 [inline]
copyin lib/iov_iter.c:165 [inline]
copy_page_from_iter_iovec lib/iov_iter.c:310 [inline]
copy_page_from_iter+0x279/0x5f0 lib/iov_iter.c:902
process_vm_rw_pages mm/process_vm_access.c:43 [inline]
process_vm_rw_single_vec+0x273/0x440 mm/process_vm_access.c:117
process_vm_rw_core mm/process_vm_access.c:215 [inline]
process_vm_rw+0x3e1/0x570 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0x76/0x90 mm/process_vm_access.c:298
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

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 22906 Comm: syz-executor.4 Not tainted 5.18.0-rc2-syzkaller-00122-gb9b4c79e5830-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.