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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1f719a2f3fa6 Merge tag 'net-6.8-rc4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13230042180000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cd0dc1b46a5bc5c
dashboard link: https://syzkaller.appspot.com/bug?extid=eb66920fb8126e450786
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/106dcd7144b4/disk-1f719a2f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5e43fabd5130/vmlinux-1f719a2f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/34491b71dd2c/bzImage-1f719a2f.xz

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

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

read-write to 0xffff88813bd317a0 of 8 bytes by task 13828 on cpu 1:
__filemap_add_folio+0x4c1/0x730 mm/filemap.c:903
filemap_add_folio+0x70/0x160 mm/filemap.c:938
page_cache_ra_unbounded+0x15e/0x2e0 mm/readahead.c:250
do_page_cache_ra mm/readahead.c:299 [inline]
page_cache_ra_order mm/readahead.c:544 [inline]
ondemand_readahead+0x50b/0x670 mm/readahead.c:666
page_cache_sync_ra+0x27e/0x2a0 mm/readahead.c:693
page_cache_sync_readahead include/linux/pagemap.h:1300 [inline]
filemap_get_pages+0x251/0xf90 mm/filemap.c:2498
filemap_splice_read+0x337/0x8f0 mm/filemap.c:2872
do_splice_read fs/splice.c:985 [inline]
splice_direct_to_actor+0x268/0x660 fs/splice.c:1089
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3b9/0x960 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1356 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0xbd/0x150 fs/read_write.c:1348
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88813bd317a0 of 8 bytes by task 13831 on cpu 0:
kiocb_invalidate_post_direct_write+0x5e/0x1b0 mm/filemap.c:3830
dio_complete+0x21b/0x480 fs/direct-io.c:301
__blockdev_direct_IO+0x1e72/0x1fa0 fs/direct-io.c:1308
blockdev_direct_IO include/linux/fs.h:3118 [inline]
fat_direct_IO+0x110/0x1d0 fs/fat/inode.c:283
generic_file_direct_write+0xab/0x1f0 mm/filemap.c:3855
__generic_file_write_iter+0xae/0x120 mm/filemap.c:4011
generic_file_write_iter+0x7d/0x1c0 mm/filemap.c:4051
call_write_iter include/linux/fs.h:2085 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x760/0x8d0 fs/read_write.c:590
ksys_write+0xeb/0x1a0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:652
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000000000000 -> 0x0000000000000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 13831 Comm: syz-executor.1 Not tainted 6.8.0-rc3-syzkaller-00136-g1f719a2f3fa6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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

[syzbot]

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