[moderation] [exfat?] KCSAN: data-race in __mark_inode_dirty / writeback_single_inode (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5e3f5b81de80 Merge tag 'net-6.7-rc5' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=114bebeee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac34c1f29a8029df
dashboard link: https://syzkaller.appspot.com/bug?extid=ab26805fb9b6d379b101
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [adilger...@dilger.ca linki...@kernel.org linux...@vger.kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org sj155...@samsung.com ty...@mit.edu]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8894c209e25f/disk-5e3f5b81.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/42757ce1a7da/vmlinux-5e3f5b81.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3314e0b4681/bzImage-5e3f5b81.xz

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

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

write to 0xffff88810659b880 of 8 bytes by task 7568 on cpu 1:
writeback_single_inode+0x10e/0x4a0 fs/fs-writeback.c:1743
sync_inode_metadata+0x56/0x80 fs/fs-writeback.c:2808
generic_buffers_fsync_noflush+0xe4/0x120 fs/buffer.c:613
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x206/0x6c0 fs/ext4/fsync.c:151
vfs_fsync_range+0x111/0x120 fs/sync.c:188
generic_write_sync include/linux/fs.h:2653 [inline]
ext4_buffered_write_iter+0x334/0x370 fs/ext4/file.c:305
ext4_file_write_iter+0x297/0xe10
do_iter_write+0x4ad/0x770 fs/read_write.c:860
vfs_iter_write+0x56/0x70 fs/read_write.c:901
iter_file_splice_write+0x462/0x7e0 fs/splice.c:736
do_splice_from fs/splice.c:933 [inline]
direct_splice_actor+0x8a/0xb0 fs/splice.c:1142
splice_direct_to_actor+0x31d/0x690 fs/splice.c:1088
do_splice_direct+0x10d/0x190 fs/splice.c:1194
do_sendfile+0x3c4/0x980 fs/read_write.c:1254
__do_sys_sendfile64 fs/read_write.c:1322 [inline]
__se_sys_sendfile64 fs/read_write.c:1308 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1308
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88810659b880 of 8 bytes by task 7570 on cpu 0:
__mark_inode_dirty+0x199/0x7d0 fs/fs-writeback.c:2474
mark_buffer_dirty+0x165/0x240 fs/buffer.c:1204
__block_write_begin_int+0x806/0xf40 fs/buffer.c:2130
__block_write_begin+0x5e/0x110 fs/buffer.c:2168
ext4_write_begin+0x41e/0xba0
ext4_da_write_begin+0x1b6/0x550 fs/ext4/inode.c:2875
generic_perform_write+0x1c9/0x410 mm/filemap.c:3918
ext4_buffered_write_iter+0x1f6/0x370 fs/ext4/file.c:299
ext4_file_write_iter+0x297/0xe10
do_iter_write+0x4ad/0x770 fs/read_write.c:860
vfs_iter_write+0x56/0x70 fs/read_write.c:901
iter_file_splice_write+0x462/0x7e0 fs/splice.c:736
do_splice_from fs/splice.c:933 [inline]
direct_splice_actor+0x8a/0xb0 fs/splice.c:1142
splice_direct_to_actor+0x31d/0x690 fs/splice.c:1088
do_splice_direct+0x10d/0x190 fs/splice.c:1194
do_sendfile+0x3c4/0x980 fs/read_write.c:1254
__do_sys_sendfile64 fs/read_write.c:1322 [inline]
__se_sys_sendfile64 fs/read_write.c:1308 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1308
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000000000007 -> 0x0000000000000084

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 7570 Comm: syz-executor.1 Not tainted 6.7.0-rc4-syzkaller-00111-g5e3f5b81de80 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================


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

[syzbot]

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