[moderation] [input?] KCSAN: data-race in evdev_pass_values / evdev_read (8)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2f51b3516da Merge tag 'rtc-6.7' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1223e17b680000
kernel config: https://syzkaller.appspot.com/x/.config?x=f89e9ee49649fd75
dashboard link: https://syzkaller.appspot.com/bug?extid=f2ad0726653a04e1016d
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/89fee4978f05/disk-d2f51b35.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/acdc29bb8759/vmlinux-d2f51b35.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6829e88f9c27/bzImage-d2f51b35.xz

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

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

write to 0xffff888103cda808 of 4 bytes by task 12964 on cpu 0:
__pass_event drivers/input/evdev.c:239 [inline]
evdev_pass_values+0x3a8/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+0x305/0x770 drivers/input/input.c:161
input_event_dispose+0x243/0x310 drivers/input/input.c:378
input_handle_event+0xac0/0xaf0 drivers/input/input.c:406
input_inject_event+0xd1/0xf0 drivers/input/input.c:465
evdev_write+0x332/0x410 drivers/input/evdev.c:530
vfs_write+0x27a/0x790 fs/read_write.c:582
ksys_write+0xeb/0x1a0 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:646
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888103cda808 of 4 bytes by task 2763 on cpu 1:
evdev_read+0x1c9/0x780 drivers/input/evdev.c:574
vfs_read+0x1a4/0x590 fs/read_write.c:468
ksys_read+0xeb/0x1a0 fs/read_write.c:613
__do_sys_read fs/read_write.c:623 [inline]
__se_sys_read fs/read_write.c:621 [inline]
__x64_sys_read+0x42/0x50 fs/read_write.c:621
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000017 -> 0x00000019

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 2763 Comm: acpid Not tainted 6.6.0-syzkaller-14651-gd2f51b3516da #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
==================================================================


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

[syzbot]

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