[moderation] [iomap?] KCSAN: data-race in __filemap_remove_folio / file_write_and_wait_range (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f06ce441457d Merge tag 'loongarch-fixes-6.10-1' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12015d0c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c00b51a1d411353
dashboard link: https://syzkaller.appspot.com/bug?extid=52b1ab7b009dee48d2db
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org djw...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e660627e9e33/disk-f06ce441.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3f59218904d3/vmlinux-f06ce441.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e2f87c4b4642/bzImage-f06ce441.xz

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

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

read-write to 0xffff888106e08788 of 8 bytes by task 31547 on cpu 1:
page_cache_delete mm/filemap.c:154 [inline]
__filemap_remove_folio+0x1c5/0x2c0 mm/filemap.c:232
invalidate_complete_folio2 mm/truncate.c:575 [inline]
invalidate_inode_pages2_range+0x447/0x710 mm/truncate.c:662
kiocb_invalidate_pages+0x1b1/0x1e0 mm/filemap.c:2738
__iomap_dio_rw+0x585/0x1090 fs/iomap/direct-io.c:639
iomap_dio_rw+0x40/0x90 fs/iomap/direct-io.c:749
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

read to 0xffff888106e08788 of 8 bytes by task 31546 on cpu 0:
mapping_needs_writeback mm/filemap.c:635 [inline]
file_write_and_wait_range+0x6d/0x170 mm/filemap.c:787
ext4_sync_file+0x134/0x6c0 fs/ext4/fsync.c:158
vfs_fsync_range+0x122/0x140 fs/sync.c:188
generic_write_sync include/linux/fs.h:2794 [inline]
ext4_buffered_write_iter+0x338/0x380 fs/ext4/file.c:305
ext4_file_write_iter+0x29f/0xe30
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: 0x0000000000000040 -> 0x000000000000003f

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 31546 Comm: syz-executor.1 Not tainted 6.10.0-rc2-syzkaller-00007-gf06ce441457d #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