KCSAN: data-race in __mark_inode_dirty / writeback_single_inode (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6a9dc5fd lib: Revert use of fallthrough pseudo-keyword in ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d23cde900000
kernel config: https://syzkaller.appspot.com/x/.config?x=8512f120b55c113f
dashboard link: https://syzkaller.appspot.com/bug?extid=fb608ef9b3cacb1fe58e
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
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+fb608e...@syzkaller.appspotmail.com

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

write to 0xffff8880bb6b02c0 of 8 bytes by task 27487 on cpu 1:
inode_sync_complete fs/fs-writeback.c:1197 [inline]
writeback_single_inode+0x4a4/0x530 fs/fs-writeback.c:1578
sync_inode fs/fs-writeback.c:2602 [inline]
sync_inode_metadata+0x52/0x70 fs/fs-writeback.c:2622
ext4_fsync_nojournal fs/ext4/fsync.c:92 [inline]
ext4_sync_file+0x335/0x6e0 fs/ext4/fsync.c:170
vfs_fsync_range+0x107/0x120 fs/sync.c:200
generic_write_sync include/linux/fs.h:2744 [inline]
ext4_buffered_write_iter+0x369/0x3b0 fs/ext4/file.c:276
ext4_file_write_iter+0x768/0x1060 include/linux/fs.h:784
call_write_iter include/linux/fs.h:1882 [inline]
do_iter_readv_writev+0x32e/0x3d0 fs/read_write.c:713
do_iter_write+0x112/0x4b0 fs/read_write.c:1018
vfs_iter_write+0x4c/0x70 fs/read_write.c:1059
iter_file_splice_write+0x41a/0x770 fs/splice.c:750
do_splice_from fs/splice.c:846 [inline]
direct_splice_actor+0x95/0x160 fs/splice.c:1016
splice_direct_to_actor+0x365/0x660 fs/splice.c:971
do_splice_direct+0xf2/0x170 fs/splice.c:1059
do_sendfile+0x56a/0xba0 fs/read_write.c:1540
__do_sys_sendfile64 fs/read_write.c:1595 [inline]
__se_sys_sendfile64 fs/read_write.c:1587 [inline]
__x64_sys_sendfile64+0xa9/0x130 fs/read_write.c:1587
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

read to 0xffff8880bb6b02c0 of 8 bytes by task 27492 on cpu 0:
__mark_inode_dirty+0xb9/0x7e0 fs/fs-writeback.c:2272
mark_buffer_dirty+0x14b/0x260 fs/buffer.c:1141
__block_commit_write fs/buffer.c:2084 [inline]
block_write_end+0x13d/0x220 fs/buffer.c:2162
generic_write_end+0x5c/0x250 fs/buffer.c:2176
ext4_da_write_end+0x57e/0x760 fs/ext4/inode.c:3091
generic_perform_write+0x23b/0x390 mm/filemap.c:3414
ext4_buffered_write_iter+0x2cc/0x3b0 fs/ext4/file.c:269
ext4_file_write_iter+0x768/0x1060 include/linux/fs.h:784
call_write_iter include/linux/fs.h:1882 [inline]
do_iter_readv_writev+0x32e/0x3d0 fs/read_write.c:713
do_iter_write+0x112/0x4b0 fs/read_write.c:1018
vfs_iter_write+0x4c/0x70 fs/read_write.c:1059
iter_file_splice_write+0x41a/0x770 fs/splice.c:750
do_splice_from fs/splice.c:846 [inline]
direct_splice_actor+0x95/0x160 fs/splice.c:1016
splice_direct_to_actor+0x365/0x660 fs/splice.c:971
do_splice_direct+0xf2/0x170 fs/splice.c:1059
do_sendfile+0x56a/0xba0 fs/read_write.c:1540
__do_sys_sendfile64 fs/read_write.c:1595 [inline]
__se_sys_sendfile64 fs/read_write.c:1587 [inline]
__x64_sys_sendfile64+0xa9/0x130 fs/read_write.c:1587
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 27492 Comm: syz-executor.5 Not tainted 5.9.0-rc2-syzkaller #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.