KCSAN: data-race in filemap_read / generic_write_end (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 26291c54e111 Linux 5.17-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17c5d2cbb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a83209f215159f48
dashboard link: https://syzkaller.appspot.com/bug?extid=e1ffd4430e9e7942349a
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

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

==================================================================
BUG: KCSAN: data-race in filemap_read / generic_write_end

write to 0xffff88810e11ac08 of 8 bytes by task 5051 on cpu 1:
i_size_write include/linux/fs.h:907 [inline]
generic_write_end+0x96/0x180 fs/buffer.c:2187
ext4_da_write_end+0x448/0x510 fs/ext4/inode.c:3042
generic_perform_write+0x261/0x400 mm/filemap.c:3776
ext4_buffered_write_iter+0x19d/0x290 fs/ext4/file.c:268
ext4_file_write_iter+0x227/0xda0
call_write_iter include/linux/fs.h:2074 [inline]
new_sync_write fs/read_write.c:503 [inline]
vfs_write+0x7f5/0x950 fs/read_write.c:590
ksys_write+0xd9/0x190 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+0x3e/0x50 fs/read_write.c:652
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff88810e11ac08 of 8 bytes by task 5064 on cpu 0:
i_size_read include/linux/fs.h:885 [inline]
filemap_read+0x1f2/0x1430 mm/filemap.c:2673
generic_file_read_iter+0x72/0x320 mm/filemap.c:2822
call_read_iter include/linux/fs.h:2068 [inline]
generic_file_splice_read+0x24f/0x330 fs/splice.c:311
do_splice_to fs/splice.c:796 [inline]
splice_direct_to_actor+0x2aa/0x650 fs/splice.c:870
do_splice_direct+0x106/0x190 fs/splice.c:979
do_sendfile+0x675/0xc40 fs/read_write.c:1245
__do_sys_sendfile64 fs/read_write.c:1310 [inline]
__se_sys_sendfile64 fs/read_write.c:1296 [inline]
__x64_sys_sendfile64+0x102/0x140 fs/read_write.c:1296
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00000000007be000 -> 0x00000000007c0000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 5064 Comm: syz-executor.1 Not tainted 5.17.0-rc2-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


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

[syzbot]

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