KCSAN: data-race in jbd2_journal_dirty_metadata / jbd2_journal_dirty_metadata

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f78d76e7 Merge tag 'drm-fixes-2021-03-12-1' of git://anong..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1067effad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5e220a5466859ca
dashboard link: https://syzkaller.appspot.com/bug?extid=e53fbe8ecf64f6d18096
compiler: Debian clang version 11.0.1-2
CC: [ja...@suse.com linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]

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+e53fbe...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in jbd2_journal_dirty_metadata / jbd2_journal_dirty_metadata

write to 0xffff888107582e84 of 4 bytes by task 14597 on cpu 0:
jbd2_journal_dirty_metadata+0x2df/0x670 fs/jbd2/transaction.c:1516
__ext4_handle_dirty_metadata+0xc6/0x590 fs/ext4/ext4_jbd2.c:331
ext4_do_update_inode fs/ext4/inode.c:5141 [inline]
ext4_mark_iloc_dirty+0x12f2/0x16f0 fs/ext4/inode.c:5724
__ext4_mark_inode_dirty+0x4db/0x5e0 fs/ext4/inode.c:5918
ext4_da_write_end+0x4c7/0x760 fs/ext4/inode.c:3102
generic_perform_write+0x23e/0x3a0 mm/filemap.c:3586
ext4_buffered_write_iter+0x2e5/0x3e0 fs/ext4/file.c:269
ext4_file_write_iter+0x48a/0x10b0 fs/ext4/file.c:502
call_write_iter include/linux/fs.h:1977 [inline]
do_iter_readv_writev+0x2cb/0x360 fs/read_write.c:740
do_iter_write+0x112/0x4c0 fs/read_write.c:866
vfs_iter_write+0x4c/0x70 fs/read_write.c:907
iter_file_splice_write+0x40a/0x750 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0x80/0xa0 fs/splice.c:936
splice_direct_to_actor+0x345/0x650 fs/splice.c:891
do_splice_direct+0xf5/0x170 fs/splice.c:979
do_sendfile+0x7a6/0xe20 fs/read_write.c:1260
__do_sys_sendfile64 fs/read_write.c:1319 [inline]
__se_sys_sendfile64 fs/read_write.c:1311 [inline]
__x64_sys_sendfile64+0xa9/0x130 fs/read_write.c:1311
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888107582e84 of 4 bytes by task 14677 on cpu 1:
jbd2_journal_dirty_metadata+0x15e/0x670 fs/jbd2/transaction.c:1484
__ext4_handle_dirty_metadata+0xc6/0x590 fs/ext4/ext4_jbd2.c:331
ext4_do_update_inode fs/ext4/inode.c:5141 [inline]
ext4_mark_iloc_dirty+0x12f2/0x16f0 fs/ext4/inode.c:5724
__ext4_mark_inode_dirty+0x4db/0x5e0 fs/ext4/inode.c:5918
ext4_da_write_end+0x4c7/0x760 fs/ext4/inode.c:3102
generic_perform_write+0x23e/0x3a0 mm/filemap.c:3586
ext4_buffered_write_iter+0x2e5/0x3e0 fs/ext4/file.c:269
ext4_file_write_iter+0x48a/0x10b0 fs/ext4/file.c:502
call_write_iter include/linux/fs.h:1977 [inline]
do_iter_readv_writev+0x2cb/0x360 fs/read_write.c:740
do_iter_write+0x112/0x4c0 fs/read_write.c:866
vfs_iter_write+0x4c/0x70 fs/read_write.c:907
iter_file_splice_write+0x40a/0x750 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0x80/0xa0 fs/splice.c:936
splice_direct_to_actor+0x345/0x650 fs/splice.c:891
do_splice_direct+0xf5/0x170 fs/splice.c:979
do_sendfile+0x7a6/0xe20 fs/read_write.c:1260
__do_sys_sendfile64 fs/read_write.c:1319 [inline]
__se_sys_sendfile64 fs/read_write.c:1311 [inline]
__x64_sys_sendfile64+0xa9/0x130 fs/read_write.c:1311
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 14677 Comm: syz-executor.4 Not tainted 5.12.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.