[moderation] [ext4?] KCSAN: data-race in __mark_inode_dirty / move_expired_inodes (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3b47bc037bd4 Merge tag 'pinctrl-v6.7-2' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1138e3aae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=585869067cd7ce59
dashboard link: https://syzkaller.appspot.com/bug?extid=7318b98ac4faf72f5c91
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 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/231e21487056/disk-3b47bc03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eae871bb6b73/vmlinux-3b47bc03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0c20f8f08d47/bzImage-3b47bc03.xz

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

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

read-write to 0xffff88819c26dd20 of 8 bytes by task 19531 on cpu 1:
move_expired_inodes+0x17b/0x410 fs/fs-writeback.c:1405
queue_io+0xe1/0x2e0 fs/fs-writeback.c:1457
wb_writeback+0x22a/0x6e0 fs/fs-writeback.c:2090
wb_do_writeback fs/fs-writeback.c:2239 [inline]
wb_workfn+0x1a8/0x8d0 fs/fs-writeback.c:2279
process_one_work kernel/workqueue.c:2630 [inline]
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
worker_thread+0x525/0x730 kernel/workqueue.c:2784
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff88819c26dd20 of 8 bytes by task 30758 on cpu 0:
__mark_inode_dirty+0x199/0x7d0 fs/fs-writeback.c:2474
mark_buffer_dirty+0x165/0x240 fs/buffer.c:1204
__block_commit_write fs/buffer.c:2191 [inline]
block_write_end+0x158/0x2e0 fs/buffer.c:2267
ext4_da_do_write_end fs/ext4/inode.c:2961 [inline]
ext4_da_write_end+0x1fc/0x9c0 fs/ext4/inode.c:3033
generic_perform_write+0x267/0x410 mm/filemap.c:3929
ext4_buffered_write_iter+0x1f6/0x370 fs/ext4/file.c:299
ext4_file_write_iter+0x297/0xe10
call_write_iter include/linux/fs.h:2020 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x48a/0x790 fs/read_write.c:584
ksys_write+0xeb/0x1a0 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:646
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000000000004 -> 0x0000000000020084

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 30758 Comm: syz-executor.4 Not tainted 6.7.0-rc3-syzkaller-00033-g3b47bc037bd4 #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