[moderation] [ext4?] KCSAN: data-race in vfs_fsync_range / writeback_single_inode (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4b377b4868ef kprobe/ftrace: fix build error due to bad fun..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11e38d92980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d11ad8b62a2732b
dashboard link: https://syzkaller.appspot.com/bug?extid=4c44219108ba2e8e8f19
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [adilger...@dilger.ca linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b00dfd3398ba/disk-4b377b48.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7f2420fe2377/vmlinux-4b377b48.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4f4f0f25329f/bzImage-4b377b48.xz

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

==================================================================
BUG: KCSAN: data-race in vfs_fsync_range / writeback_single_inode

write to 0xffff8881069173f0 of 8 bytes by task 4140 on cpu 0:
writeback_single_inode+0x10e/0x4a0 fs/fs-writeback.c:1769
sync_inode_metadata+0x5c/0x90 fs/fs-writeback.c:2842
generic_buffers_fsync_noflush+0xe4/0x130 fs/buffer.c:612
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x20b/0x6c0 fs/ext4/fsync.c:151
vfs_fsync_range+0x122/0x140 fs/sync.c:188
generic_write_sync include/linux/fs.h:2811 [inline]
ext4_buffered_write_iter+0x338/0x380 fs/ext4/file.c:305
ext4_file_write_iter+0x29f/0xe30
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 0xffff8881069173f0 of 8 bytes by task 4126 on cpu 1:
vfs_fsync_range+0xa6/0x140 fs/sync.c:186
generic_write_sync include/linux/fs.h:2811 [inline]
ext4_buffered_write_iter+0x338/0x380 fs/ext4/file.c:305
ext4_file_write_iter+0x29f/0xe30
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: 0x0000000000000007 -> 0x0000000000000080

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4126 Comm: syz-executor.1 Not tainted 6.9.0-syzkaller-08544-g4b377b4868ef #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