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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 861c0981648f Merge tag 'jfs-6.8-rc3' of github.com:kleikam..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1331bc40180000
kernel config: https://syzkaller.appspot.com/x/.config?x=243bc832fc3f4a47
dashboard link: https://syzkaller.appspot.com/bug?extid=97faf925ac670f762aab
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/d2cf8d6fed8c/disk-861c0981.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eae4d13f14d3/vmlinux-861c0981.xz
kernel image: https://storage.googleapis.com/syzbot-assets/27c559bdbfbf/bzImage-861c0981.xz

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

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

read-write to 0xffff888107d7f3f0 of 8 bytes by task 38 on cpu 1:
redirty_tail_locked+0x56/0x270 fs/fs-writeback.c:1322
requeue_inode fs/fs-writeback.c:1583 [inline]
writeback_sb_inodes+0x7dd/0xad0 fs/fs-writeback.c:1945
wb_writeback+0x252/0x6e0 fs/fs-writeback.c:2092
wb_do_writeback fs/fs-writeback.c:2239 [inline]
wb_workfn+0x1a8/0x8d0 fs/fs-writeback.c:2279
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
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 0xffff888107d7f3f0 of 8 bytes by task 11270 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:2175 [inline]
block_write_end+0x158/0x2e0 fs/buffer.c:2251
ext4_da_do_write_end fs/ext4/inode.c:2961 [inline]
ext4_da_write_end+0x1ad/0x860 fs/ext4/inode.c:3034
generic_perform_write+0x267/0x410 mm/filemap.c:3941
ext4_buffered_write_iter+0x1f6/0x370 fs/ext4/file.c:299
ext4_file_write_iter+0x297/0xe10
__kernel_write_iter+0x25f/0x480 fs/read_write.c:523
dump_emit_page fs/coredump.c:888 [inline]
dump_user_range+0x25d/0x480 fs/coredump.c:915
elf_core_dump+0x1a85/0x1ba0 fs/binfmt_elf.c:2077
do_coredump+0x102a/0x1890 fs/coredump.c:764
get_signal+0xdb5/0x10a0 kernel/signal.c:2879
arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:105 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
irqentry_exit_to_user_mode+0x98/0x130 kernel/entry/common.c:225
irqentry_exit+0x12/0x40 kernel/entry/common.c:328
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

value changed: 0x0000000000020085 -> 0x0000000000000005

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11270 Comm: syz-executor.2 Not tainted 6.8.0-rc2-syzkaller-00031-g861c0981648f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/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.