[moderation] [input?] KCSAN: data-race in evdev_pass_values / evdev_poll (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3c999d1ae3c7 Merge tag 'wq-for-6.10' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10540ee4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=41b6b83a95ebb268
dashboard link: https://syzkaller.appspot.com/bug?extid=2abd0ef237509f4d1b20
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [dmitry....@gmail.com 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/3202939b3e7a/disk-3c999d1a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/95266f6b0d61/vmlinux-3c999d1a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0484a1ee0e68/bzImage-3c999d1a.xz

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

==================================================================
BUG: KCSAN: data-race in evdev_pass_values / evdev_poll

write to 0xffff888104046008 of 4 bytes by task 14529 on cpu 1:
__pass_event drivers/input/evdev.c:239 [inline]
evdev_pass_values+0x3ac/0x510 drivers/input/evdev.c:278
evdev_events+0x90/0xd0 drivers/input/evdev.c:306
input_to_handler drivers/input/input.c:129 [inline]
input_pass_values+0x309/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/0x8e0 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+0x27b7/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888104046008 of 4 bytes by task 2777 on cpu 0:
evdev_poll+0xe4/0x120 drivers/input/evdev.c:623
vfs_poll include/linux/poll.h:84 [inline]
do_select+0x959/0xfa0 fs/select.c:538
core_sys_select+0x362/0x530 fs/select.c:681
do_pselect fs/select.c:763 [inline]
__do_sys_pselect6 fs/select.c:804 [inline]
__se_sys_pselect6+0x213/0x280 fs/select.c:795
__x64_sys_pselect6+0x78/0x90 fs/select.c:795
x64_sys_call+0xe7b/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:271
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000b -> 0x0000000d

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 2777 Comm: acpid Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #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