[moderation] [fs?] [mm?] KCSAN: data-race in __filemap_add_folio / kiocb_invalidate_post_direct_write (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7c16f0a4ed1c Merge tag 'i2c-for-6.10-rc5' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=103dafb1980000
kernel config: https://syzkaller.appspot.com/x/.config?x=704451bc2941bcb0
dashboard link: https://syzkaller.appspot.com/bug?extid=345825cd2023c1bfe16f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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/9acd4869df3e/disk-7c16f0a4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a5b6e853a6e5/vmlinux-7c16f0a4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23b225386827/bzImage-7c16f0a4.xz

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

==================================================================
BUG: KCSAN: data-race in __filemap_add_folio / kiocb_invalidate_post_direct_write

read-write to 0xffff888107cf2c08 of 8 bytes by task 28351 on cpu 1:
__filemap_add_folio+0x439/0x710 mm/filemap.c:918
filemap_add_folio+0x9c/0x1b0 mm/filemap.c:970
page_cache_ra_unbounded+0x148/0x2e0 mm/readahead.c:252
do_page_cache_ra mm/readahead.c:303 [inline]
page_cache_ra_order mm/readahead.c:547 [inline]
ondemand_readahead+0x542/0x6b0 mm/readahead.c:669
page_cache_sync_ra+0xe0/0xf0 mm/readahead.c:696
page_cache_sync_readahead include/linux/pagemap.h:1306 [inline]
filemap_get_pages+0x252/0xfb0 mm/filemap.c:2529
filemap_splice_read+0x360/0x920 mm/filemap.c:2894
ext4_file_splice_read+0x95/0xc0 fs/ext4/file.c:158
do_splice_read fs/splice.c:985 [inline]
splice_direct_to_actor+0x26c/0x670 fs/splice.c:1089
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3ab/0x960 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1348
x64_sys_call+0x2c9f/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888107cf2c08 of 8 bytes by task 28355 on cpu 0:
kiocb_invalidate_post_direct_write+0x5e/0x1b0 mm/filemap.c:3915
iomap_dio_complete+0x33a/0x4c0 fs/iomap/direct-io.c:114
iomap_dio_rw+0x62/0x90 fs/iomap/direct-io.c:753
ext4_dio_write_iter fs/ext4/file.c:577 [inline]
ext4_file_write_iter+0xaa4/0xe30 fs/ext4/file.c:696
iter_file_splice_write+0x5e6/0x970 fs/splice.c:743
do_splice_from fs/splice.c:941 [inline]
direct_splice_actor+0x16c/0x2c0 fs/splice.c:1164
splice_direct_to_actor+0x305/0x670 fs/splice.c:1108
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3ab/0x960 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1348
x64_sys_call+0x2c9f/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000263 -> 0x0000000000000266

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 28355 Comm: syz-executor.1 Tainted: G W 6.10.0-rc4-syzkaller-00330-g7c16f0a4ed1c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
==================================================================


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