KCSAN: data-race in evdev_pass_values / evdev_read (3)

8 views
Skip to first unread message

syzbot

unread,
May 17, 2022, 9:01:31 AM5/17/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 42226c989789 Linux 5.18-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146bb295f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=83a97198b5da3a53
dashboard link: https://syzkaller.appspot.com/bug?extid=ebb2a29c729a15afa998
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [dmitry....@gmail.com linux...@vger.kernel.org linux-...@vger.kernel.org ryd...@bitmath.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+ebb2a2...@syzkaller.appspotmail.com

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

write to 0xffff888104914808 of 4 bytes by task 10750 on cpu 1:
__pass_event drivers/input/evdev.c:239 [inline]
evdev_pass_values+0x3b7/0x510 drivers/input/evdev.c:278
evdev_events+0x91/0xd0 drivers/input/evdev.c:306
input_to_handler drivers/input/input.c:126 [inline]
input_pass_values+0x37a/0x8f0 drivers/input/input.c:156
input_handle_event+0x8d4/0xd50 drivers/input/input.c:415
input_inject_event+0xbc/0xe0 drivers/input/input.c:487
evdev_write+0x326/0x400 drivers/input/evdev.c:530
vfs_write+0x26d/0x890 fs/read_write.c:589
ksys_write+0xe8/0x1a0 fs/read_write.c:644
__do_sys_write fs/read_write.c:656 [inline]
__se_sys_write fs/read_write.c:653 [inline]
__x64_sys_write+0x3e/0x50 fs/read_write.c:653
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888104914808 of 4 bytes by task 1424 on cpu 0:
evdev_read+0x1c5/0x7a0 drivers/input/evdev.c:574
vfs_read+0x1a1/0x6a0 fs/read_write.c:480
ksys_read+0xe8/0x1a0 fs/read_write.c:620
__do_sys_read fs/read_write.c:630 [inline]
__se_sys_read fs/read_write.c:628 [inline]
__x64_sys_read+0x3e/0x50 fs/read_write.c:628
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00000026 -> 0x00000028

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1424 Comm: acpid Not tainted 5.18.0-rc7-syzkaller-dirty #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

unread,
Aug 3, 2022, 7:33:13 PM8/3/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages