KCSAN: data-race in __ps2_command / ps2_handle_response

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 13311e74 Linux 5.13-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1518f984300000
kernel config: https://syzkaller.appspot.com/x/.config?x=a702dbad4961cdfa
dashboard link: https://syzkaller.appspot.com/bug?extid=b0d19ddf7d0bfa335ed6
compiler: Debian clang version 11.0.1-2
CC: [dmitry....@gmail.com gusta...@kernel.org linux...@vger.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+b0d19d...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in __ps2_command / ps2_handle_response

write to 0xffff888101adec60 of 1 bytes by interrupt on cpu 0:
ps2_handle_response+0x40/0x140 drivers/input/serio/libps2.c:463
psmouse_interrupt+0x6d4/0x930 drivers/input/mouse/psmouse-base.c:369
serio_interrupt+0x5d/0xe0 drivers/input/serio/serio.c:1002
i8042_interrupt+0x39e/0x720 drivers/input/serio/i8042.c:602
__handle_irq_event_percpu+0x93/0x3f0 kernel/irq/handle.c:156
handle_irq_event_percpu kernel/irq/handle.c:196 [inline]
handle_irq_event+0xb0/0x160 kernel/irq/handle.c:213
handle_edge_irq+0x17e/0x600 kernel/irq/chip.c:819
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0x38/0xb0 arch/x86/kernel/irq.c:250
common_interrupt+0x73/0x90 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x1e/0x40 arch/x86/include/asm/idtentry.h:638
native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
acpi_safe_halt drivers/acpi/processor_idle.c:108 [inline]
acpi_idle_do_entry drivers/acpi/processor_idle.c:513 [inline]
acpi_idle_enter+0x25b/0x2e0 drivers/acpi/processor_idle.c:648
cpuidle_enter_state+0x2b6/0x750 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x3c/0x60 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:158 [inline]
cpuidle_idle_call kernel/sched/idle.c:239 [inline]
do_idle+0x1a3/0x240 kernel/sched/idle.c:306
cpu_startup_entry+0x15/0x20 kernel/sched/idle.c:403
rest_init+0xc9/0xd0 init/main.c:721
arch_call_rest_init+0xa/0xb
start_kernel+0x59e/0x623 init/main.c:1087
secondary_startup_64_no_verify+0xb0/0xbb

read to 0xffff888101adec60 of 1 bytes by task 9210 on cpu 1:
__ps2_command+0x4f8/0xa40 drivers/input/serio/libps2.c:288
ps2_command+0x51/0x90 drivers/input/serio/libps2.c:332
alps_rpt_cmd+0x122/0x140 drivers/input/mouse/alps.c:1782
alps_identify+0x104/0x1770 drivers/input/mouse/alps.c:2905
alps_detect+0x2d/0x220 drivers/input/mouse/alps.c:3178
psmouse_do_detect drivers/input/mouse/psmouse-base.c:1009 [inline]
psmouse_try_protocol drivers/input/mouse/psmouse-base.c:1023 [inline]
psmouse_extensions+0xda8/0x1790 drivers/input/mouse/psmouse-base.c:1154
__psmouse_reconnect+0x31e/0x620 drivers/input/mouse/psmouse-base.c:1728
psmouse_reconnect+0x13/0x20 drivers/input/mouse/psmouse-base.c:1766
serio_reconnect_driver drivers/input/serio/serio.c:59 [inline]
serio_reconnect_port drivers/input/serio/serio.c:588 [inline]
serio_handle_event+0x6be/0xc20 drivers/input/serio/serio.c:214
process_one_work+0x3e9/0x8f0 kernel/workqueue.c:2276
worker_thread+0x636/0xae0 kernel/workqueue.c:2422
kthread+0x1d0/0x1f0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

value changed: 0x02 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 9210 Comm: kworker/1:5 Not tainted 5.13.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_long serio_handle_event
==================================================================


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