[moderation] [mm?] KCSAN: data-race in _copy_to_iter / copy_folio_from_iter_atomic (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c64efcb083c Merge tag 'rust-rustfmt' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1686e492580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4c8075c5c889049
dashboard link: https://syzkaller.appspot.com/bug?extid=e28bd6fd306dd4ff1468
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
CC: [ak...@linux-foundation.org baoli...@linux.alibaba.com hu...@google.com linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b479de7224e1/disk-1c64efcb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aa6dca180537/vmlinux-1c64efcb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca14c4d6f266/bzImage-1c64efcb.xz

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

==================================================================
BUG: KCSAN: data-race in _copy_to_iter / copy_folio_from_iter_atomic

write to 0xffff88812f97f45a of 46 bytes by task 12052 on cpu 1:
memcpy_from_iter lib/iov_iter.c:73 [inline]
iterate_bvec include/linux/iov_iter.h:123 [inline]
iterate_and_advance2 include/linux/iov_iter.h:306 [inline]
iterate_and_advance include/linux/iov_iter.h:330 [inline]
__copy_from_iter lib/iov_iter.c:249 [inline]
copy_folio_from_iter_atomic+0x7fc/0x11b0 lib/iov_iter.c:479
generic_perform_write+0x2c2/0x490 mm/filemap.c:4260
shmem_file_write_iter+0xc5/0xf0 mm/shmem.c:3464
iter_file_splice_write+0x666/0xa60 fs/splice.c:738
do_splice_from fs/splice.c:938 [inline]
direct_splice_actor+0x156/0x2a0 fs/splice.c:1161
splice_direct_to_actor+0x312/0x680 fs/splice.c:1105
do_splice_direct_actor fs/splice.c:1204 [inline]
do_splice_direct+0xda/0x150 fs/splice.c:1230
do_sendfile+0x380/0x650 fs/read_write.c:1370
__do_sys_sendfile64 fs/read_write.c:1431 [inline]
__se_sys_sendfile64 fs/read_write.c:1417 [inline]
__x64_sys_sendfile64+0x105/0x150 fs/read_write.c:1417
x64_sys_call+0x2bb4/0x3000 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88812f97f45a of 46 bytes by task 12050 on cpu 0:
memcpy_to_iter lib/iov_iter.c:65 [inline]
iterate_bvec include/linux/iov_iter.h:123 [inline]
iterate_and_advance2 include/linux/iov_iter.h:306 [inline]
iterate_and_advance include/linux/iov_iter.h:330 [inline]
_copy_to_iter+0x602/0xe70 lib/iov_iter.c:185
copy_page_to_iter+0x18f/0x2d0 lib/iov_iter.c:362
copy_folio_to_iter include/linux/uio.h:204 [inline]
shmem_file_read_iter+0x2d6/0x540 mm/shmem.c:3412
copy_splice_read+0x442/0x660 fs/splice.c:363
do_splice_read fs/splice.c:981 [inline]
splice_direct_to_actor+0x290/0x680 fs/splice.c:1086
do_splice_direct_actor fs/splice.c:1204 [inline]
do_splice_direct+0xda/0x150 fs/splice.c:1230
do_sendfile+0x380/0x650 fs/read_write.c:1370
__do_sys_sendfile64 fs/read_write.c:1431 [inline]
__se_sys_sendfile64 fs/read_write.c:1417 [inline]
__x64_sys_sendfile64+0x105/0x150 fs/read_write.c:1417
x64_sys_call+0x2bb4/0x3000 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 12050 Comm: syz.2.3276 Not tainted syzkaller #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
==================================================================


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup