[moderation] [serial?] KCSAN: data-race in console_callback / kbd_event (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c3f38fa61af7 Linux 6.10-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=156d6d64980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c00b51a1d411353
dashboard link: https://syzkaller.appspot.com/bug?extid=a66efb2ca07765365aee
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org jiri...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eef327542baf/disk-c3f38fa6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8e83b758a6a4/vmlinux-c3f38fa6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/132dca419132/bzImage-c3f38fa6.xz

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

==================================================================
BUG: KCSAN: data-race in console_callback / kbd_event

read to 0xffffffff88449ad0 of 4 bytes by task 20251 on cpu 1:
console_callback+0x126/0x300 drivers/tty/vt/vt.c:3133
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

write to 0xffffffff88449ad0 of 4 bytes by task 26826 on cpu 0:
kbd_event+0x1c05/0x1e90 drivers/tty/vt/keyboard.c:1548
input_to_handler drivers/input/input.c:132 [inline]
input_pass_values+0x3a5/0x790 drivers/input/input.c:161
input_event_dispose+0x251/0x320 drivers/input/input.c:378
input_handle_event+0xac4/0xb00 drivers/input/input.c:406
input_inject_event+0xd1/0x100 drivers/input/input.c:465
evdev_write+0x334/0x420 drivers/input/evdev.c:530
vfs_write+0x28b/0x900 fs/read_write.c:588
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

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 26826 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
==================================================================


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