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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 037266a5f723 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=170b289f680000
kernel config: https://syzkaller.appspot.com/x/.config?x=a91f789b98394377
dashboard link: https://syzkaller.appspot.com/bug?extid=d0025f336f56c1feee91
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/82a19416792d/disk-037266a5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b4c696534428/vmlinux-037266a5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c7ee3569aaa5/bzImage-037266a5.xz

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

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

write to 0xffff88818bb2e880 of 4 bytes by task 21926 on cpu 0:
do_sync_mmap_readahead+0x3de/0x450 mm/filemap.c:3138
filemap_fault+0x426/0xc30 mm/filemap.c:3233
__do_fault mm/memory.c:4265 [inline]
do_read_fault mm/memory.c:4628 [inline]
do_fault mm/memory.c:4762 [inline]
do_pte_missing mm/memory.c:3730 [inline]
handle_pte_fault mm/memory.c:5038 [inline]
__handle_mm_fault mm/memory.c:5179 [inline]
handle_mm_fault+0x13bd/0x2dd0 mm/memory.c:5344
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:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read-write to 0xffff88818bb2e880 of 4 bytes by task 21938 on cpu 1:
read_pages+0x23c/0x530 mm/readahead.c:170
page_cache_ra_unbounded+0x2aa/0x2e0 mm/readahead.c:269
do_page_cache_ra mm/readahead.c:299 [inline]
page_cache_ra_order mm/readahead.c:546 [inline]
ondemand_readahead+0x524/0x690 mm/readahead.c:668
page_cache_async_ra+0x94/0xa0 mm/readahead.c:717
do_async_mmap_readahead mm/filemap.c:3169 [inline]
filemap_fault+0x3da/0xc30 mm/filemap.c:3223
__do_fault mm/memory.c:4265 [inline]
do_read_fault mm/memory.c:4628 [inline]
do_fault mm/memory.c:4762 [inline]
do_pte_missing mm/memory.c:3730 [inline]
handle_pte_fault mm/memory.c:5038 [inline]
__handle_mm_fault mm/memory.c:5179 [inline]
handle_mm_fault+0x13bd/0x2dd0 mm/memory.c:5344
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:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000b -> 0x0000001f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 21938 Comm: syz-executor.3 Not tainted 6.7.0-rc1-syzkaller-00344-g037266a5f723 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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

[syzbot]

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