[moderation] [fs?] [mm?] KCSAN: data-race in page_cache_sync_ra / page_cache_sync_ra (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 561c80369df0 Merge tag 'tty-6.16-rc1-2' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1650b1a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7136549ecfde7285
dashboard link: https://syzkaller.appspot.com/bug?extid=304b197a7d8f4ed89c75
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org wi...@infradead.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/40354c23f6ca/disk-561c8036.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6ccd17329ea8/vmlinux-561c8036.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bb051b8d17ea/bzImage-561c8036.xz

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

EXT4-fs (loop5): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop5): 1 truncate cleaned up
EXT4-fs (loop5): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
==================================================================
BUG: KCSAN: data-race in page_cache_sync_ra / page_cache_sync_ra

write to 0xffff8881227add50 of 8 bytes by task 5685 on cpu 0:
page_cache_sync_ra+0x434/0x6c0 mm/readahead.c:584
filemap_get_pages+0x2d0/0x1150 mm/filemap.c:2603
filemap_splice_read+0x3a9/0x740 mm/filemap.c:2991
ext4_file_splice_read+0x8f/0xb0 fs/ext4/file.c:158
do_splice_read fs/splice.c:979 [inline]
splice_direct_to_actor+0x26f/0x680 fs/splice.c:1083
do_splice_direct_actor fs/splice.c:1201 [inline]
do_splice_direct+0xda/0x150 fs/splice.c:1227
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+0x2bb0/0x2ff0 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

write to 0xffff8881227add50 of 8 bytes by task 5682 on cpu 1:
page_cache_sync_ra+0x434/0x6c0 mm/readahead.c:584
filemap_get_pages+0x2d0/0x1150 mm/filemap.c:2603
filemap_splice_read+0x3a9/0x740 mm/filemap.c:2991
ext4_file_splice_read+0x8f/0xb0 fs/ext4/file.c:158
do_splice_read fs/splice.c:979 [inline]
splice_direct_to_actor+0x26f/0x680 fs/splice.c:1083
do_splice_direct_actor fs/splice.c:1201 [inline]
do_splice_direct+0xda/0x150 fs/splice.c:1227
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+0x2bb0/0x2ff0 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

value changed: 0x0000000000000000 -> 0x0000000000000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 5682 Comm: syz.5.738 Not tainted 6.16.0-syzkaller-12256-g561c80369df0 #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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

[syzbot]

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