[moderation] [ext4?] KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 83a7eefedc9b Linux 6.10-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1584897e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=68336ea4b6f4fc09
dashboard link: https://syzkaller.appspot.com/bug?extid=3e565959df8ce2f9b21b
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/dc4448d7f810/disk-83a7eefe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1b7e727f29b/vmlinux-83a7eefe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/470dd9374113/bzImage-83a7eefe.xz

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

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

read-write to 0xffff888106af2f60 of 8 bytes by task 12930 on cpu 1:
redirty_tail_locked+0x56/0x270 fs/fs-writeback.c:1346
requeue_inode fs/fs-writeback.c:1609 [inline]
writeback_sb_inodes+0x903/0xb20 fs/fs-writeback.c:1976
__writeback_inodes_wb+0x9a/0x1a0 fs/fs-writeback.c:2018
wb_writeback+0x270/0x720 fs/fs-writeback.c:2129
wb_check_start_all fs/fs-writeback.c:2255 [inline]
wb_do_writeback fs/fs-writeback.c:2281 [inline]
wb_workfn+0x4ea/0x940 fs/fs-writeback.c:2314
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3312
worker_thread+0x526/0x730 kernel/workqueue.c:3393
kthread+0x1d1/0x210 kernel/kthread.c:389
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff888106af2f60 of 8 bytes by task 2428 on cpu 0:
__mark_inode_dirty+0x19f/0x7e0 fs/fs-writeback.c:2508
mark_buffer_dirty+0x165/0x250 fs/buffer.c:1211
__block_commit_write fs/buffer.c:2200 [inline]
block_write_end+0x158/0x2e0 fs/buffer.c:2276
ext4_da_do_write_end fs/ext4/inode.c:2952 [inline]
ext4_da_write_end+0x1ad/0x860 fs/ext4/inode.c:3025
generic_perform_write+0x276/0x410 mm/filemap.c:4026
ext4_buffered_write_iter+0x1f6/0x380 fs/ext4/file.c:299
ext4_file_write_iter+0x29f/0xe30
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x78f/0x900 fs/read_write.c:590
ksys_write+0xeb/0x1b0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:652
x64_sys_call+0x27ef/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f



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