[moderation] [mm?] KCSAN: data-race in __filemap_remove_folio / kiocb_invalidate_post_direct_write

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ea5f6ad9ad96 Merge tag 'platform-drivers-x86-v6.10-1' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ebfcd0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d11ad8b62a2732b
dashboard link: https://syzkaller.appspot.com/bug?extid=e8616ca5a8d283d94778
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/92ffd793960a/disk-ea5f6ad9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a1f992e8f978/vmlinux-ea5f6ad9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/38099d58c151/bzImage-ea5f6ad9.xz

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

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

read-write to 0xffff8881043e79b8 of 8 bytes by task 5506 on cpu 1:
page_cache_delete mm/filemap.c:154 [inline]
__filemap_remove_folio+0x1c5/0x2c0 mm/filemap.c:232
__remove_mapping+0x341/0x470 mm/vmscan.c:762
remove_mapping+0x22/0x90 mm/vmscan.c:795
mapping_evict_folio mm/truncate.c:293 [inline]
mapping_try_invalidate+0x288/0x3e0 mm/truncate.c:511
invalidate_mapping_pages+0x27/0x40 mm/truncate.c:549
ext4_dio_write_iter fs/ext4/file.c:619 [inline]
ext4_file_write_iter+0xdca/0xe30 fs/ext4/file.c:696
call_write_iter include/linux/fs.h:2120 [inline]
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+0x3b9/0x970 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+0x2c67/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:41
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+0x77/0x7f

read to 0xffff8881043e79b8 of 8 bytes by task 5509 on cpu 0:
kiocb_invalidate_post_direct_write+0x5e/0x1b0 mm/filemap.c:3874
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
call_write_iter include/linux/fs.h:2120 [inline]
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+0x3b9/0x970 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+0x2c67/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:41
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+0x77/0x7f

value changed: 0x000000000000001d -> 0x0000000000000011

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 5509 Comm: syz-executor.0 Not tainted 6.9.0-syzkaller-08284-gea5f6ad9ad96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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