[moderation] [mm?] KCSAN: data-race in do_sync_mmap_readahead / do_sync_mmap_readahead (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 453f5db0619e Merge tag 'trace-v6.7-rc7' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a48c19e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4da1e2da456c3a7d
dashboard link: https://syzkaller.appspot.com/bug?extid=54d878f388c40ef735d6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org 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/c9da66f61dd6/disk-453f5db0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8e7a5604afa2/vmlinux-453f5db0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/323c3d73a7c1/bzImage-453f5db0.xz

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

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

write to 0xffff8881573acb78 of 8 bytes by task 19011 on cpu 1:
do_sync_mmap_readahead+0x3ce/0x450 mm/filemap.c:3146
filemap_fault+0x426/0xc30 mm/filemap.c:3242
__do_fault mm/memory.c:4266 [inline]
do_read_fault mm/memory.c:4629 [inline]
do_fault mm/memory.c:4763 [inline]
do_pte_missing mm/memory.c:3731 [inline]
handle_pte_fault mm/memory.c:5039 [inline]
__handle_mm_fault mm/memory.c:5180 [inline]
handle_mm_fault+0x13bd/0x2dd0 mm/memory.c:5345
faultin_page mm/gup.c:956 [inline]
__get_user_pages+0x402/0xe40 mm/gup.c:1239
populate_vma_page_range mm/gup.c:1677 [inline]
__mm_populate+0x216/0x330 mm/gup.c:1786
mm_populate include/linux/mm.h:3379 [inline]
vm_mmap_pgoff+0x1a7/0x240 mm/util.c:561
ksys_mmap_pgoff+0x2b8/0x330 mm/mmap.c:1425
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

write to 0xffff8881573acb78 of 8 bytes by task 18997 on cpu 0:
do_sync_mmap_readahead+0x3ce/0x450 mm/filemap.c:3146
filemap_fault+0x426/0xc30 mm/filemap.c:3242
__do_fault mm/memory.c:4266 [inline]
do_read_fault mm/memory.c:4629 [inline]
do_fault mm/memory.c:4763 [inline]
do_pte_missing mm/memory.c:3731 [inline]
handle_pte_fault mm/memory.c:5039 [inline]
__handle_mm_fault mm/memory.c:5180 [inline]
handle_mm_fault+0x13bd/0x2dd0 mm/memory.c:5345
faultin_page mm/gup.c:956 [inline]
__get_user_pages+0x402/0xe40 mm/gup.c:1239
populate_vma_page_range mm/gup.c:1677 [inline]
__mm_populate+0x216/0x330 mm/gup.c:1786
mm_populate include/linux/mm.h:3379 [inline]
vm_mmap_pgoff+0x1a7/0x240 mm/util.c:561
ksys_mmap_pgoff+0x2b8/0x330 mm/mmap.c:1425
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000000000001a5 -> 0x00000000000001a6

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 18997 Comm: syz-executor.0 Not tainted 6.7.0-rc7-syzkaller-00049-g453f5db0619e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
==================================================================


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