KCSAN: data-race in console_callback / kbd_event

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 407ab579 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e3ac3a500000
kernel config: https://syzkaller.appspot.com/x/.config?x=671e27f23e60a67b
dashboard link: https://syzkaller.appspot.com/bug?extid=243eaddc739399cdeef8
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [gre...@linuxfoundation.org jiri...@kernel.org linux-...@vger.kernel.org]

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

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

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

read to 0xffffffff88bd8f40 of 4 bytes by task 4878 on cpu 1:
console_callback+0x122/0x2f0 drivers/tty/vt/vt.c:2953
process_one_work+0x3e1/0x950 kernel/workqueue.c:2272
worker_thread+0x635/0xb90 kernel/workqueue.c:2418
kthread+0x1fa/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

write to 0xffffffff88bd8f40 of 4 bytes by interrupt on cpu 0:
kbd_event+0x19cc/0x1f10 drivers/tty/vt/keyboard.c:1512
input_to_handler drivers/input/input.c:118 [inline]
input_pass_values+0x46d/0x8f0 drivers/input/input.c:145
input_handle_event+0x90d/0xd30 drivers/input/input.c:410
input_event+0x7d/0xa0 drivers/input/input.c:441
hidinput_hid_event+0xa84/0xb90 drivers/hid/hid-input.c:1396
hid_process_event+0x2f3/0x3c0 drivers/hid/hid-core.c:1519
hid_input_field drivers/hid/hid-core.c:1577 [inline]
hid_report_raw_event+0xb96/0xd60 drivers/hid/hid-core.c:1783
hid_input_report+0x2c9/0x330 drivers/hid/hid-core.c:1850
hid_irq_in+0x2cb/0x3d0 drivers/hid/usbhid/hid-core.c:284
__usb_hcd_giveback_urb+0x219/0x290 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0xae/0x210 drivers/usb/core/hcd.c:1716
dummy_timer+0x4d3/0x2390 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x2e/0x240 kernel/time/timer.c:1410
expire_timers+0x116/0x260 kernel/time/timer.c:1455
__run_timers+0x328/0x3c0 kernel/time/timer.c:1747
run_timer_softirq+0x19/0x30 kernel/time/timer.c:1760
__do_softirq+0x12c/0x2b1 kernel/softirq.c:298
asm_call_irq_on_stack+0xf/0x20
__run_on_irqstack arch/x86/include/asm/irq_stack.h:26 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:77 [inline]
do_softirq_own_stack+0x32/0x40 arch/x86/kernel/irq_64.c:77
invoke_softirq kernel/softirq.c:393 [inline]
__irq_exit_rcu+0xb2/0xc0 kernel/softirq.c:423
sysvec_apic_timer_interrupt+0x74/0x90 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:631
native_safe_halt arch/x86/include/asm/irqflags.h:60 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:103 [inline]
acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
acpi_idle_do_entry drivers/acpi/processor_idle.c:517 [inline]
acpi_idle_enter+0x25b/0x2e0 drivers/acpi/processor_idle.c:648
cpuidle_enter_state+0x2bd/0x750 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x3c/0x60 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:132 [inline]
cpuidle_idle_call kernel/sched/idle.c:213 [inline]
do_idle+0x193/0x230 kernel/sched/idle.c:273
cpu_startup_entry+0x15/0x20 kernel/sched/idle.c:369
rest_init+0xd7/0xe0 init/main.c:711
arch_call_rest_init+0xa/0xb
start_kernel+0x5a0/0x625 init/main.c:1051
secondary_startup_64_no_verify+0xb0/0xbb

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


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

[syzbot]

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