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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 499551201b5f Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=164eef30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=67aa69407438e9cf
dashboard link: https://syzkaller.appspot.com/bug?extid=2c78d0298bd8bcab1670
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/c483c0e0089f/disk-49955120.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/92a93ab3fbb1/vmlinux-49955120.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ffbe49023f4/bzImage-49955120.xz

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

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

write to 0xffff8881045d6008 of 4 bytes by task 6955 on cpu 0:
__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_pass_values+0x11a/0x390 drivers/input/input.c:126
input_event_dispose+0x232/0x300 drivers/input/input.c:341
input_handle_event+0xac4/0xb00 drivers/input/input.c:369
input_inject_event+0xd1/0x100 drivers/input/input.c:428
evdev_write+0x33f/0x440 drivers/input/evdev.c:528
vfs_write+0x281/0x920 fs/read_write.c:677
ksys_write+0xe8/0x1b0 fs/read_write.c:731
__do_sys_write fs/read_write.c:742 [inline]
__se_sys_write fs/read_write.c:739 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:739
x64_sys_call+0x287e/0x2dc0 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

read to 0xffff8881045d6008 of 4 bytes by task 2983 on cpu 1:
evdev_poll+0xde/0x120 drivers/input/evdev.c:621
vfs_poll include/linux/poll.h:84 [inline]
select_poll_one fs/select.c:480 [inline]
do_select+0x8d4/0xfc0 fs/select.c:536
core_sys_select+0x362/0x530 fs/select.c:677
do_pselect fs/select.c:759 [inline]
__do_sys_pselect6 fs/select.c:802 [inline]
__se_sys_pselect6+0x20d/0x270 fs/select.c:793
__x64_sys_pselect6+0x78/0x90 fs/select.c:793
x64_sys_call+0x2ac2/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:271
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: 0x0000000e -> 0x00000010

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 2983 Comm: acpid Not tainted 6.13.0-rc3-syzkaller-00209-g499551201b5f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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