From: syzbot <syzbot+13cb3b01d0784e4ffc3f@syzkaller.appspotmail.com>
To: aaron.ma@canonical.com, aduggan@synaptics.com,
benjamin.tissoires@redhat.com, dmitry.torokhov@gmail.com,
kt.liao@emc.com.tw, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, peter.hutterer@who-t.net,
rydberg@bitmath.org, syzkaller-bugs@googlegroups.com,
zhenjie.wang@sjtu.edu.cn
Subject: KMSAN: uninit-value in synaptics_detect
Date: Thu, 20 Sep 2018 14:04:04 -0700 [thread overview]
Message-ID: <000000000000f0575a057653dc12@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 42a037ca8d9d kmsan: update README.md to reference LLVM r34..
git tree: https://github.com/google/kmsan.git/master
console output: https://syzkaller.appspot.com/x/log.txt?x=1392c149400000
kernel config: https://syzkaller.appspot.com/x/.config?x=3431f03869413153
dashboard link: https://syzkaller.appspot.com/bug?extid=13cb3b01d0784e4ffc3f
compiler: clang version 8.0.0 (trunk 339414)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14616421400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16a164d1400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+13cb3b01d0784e4ffc3f@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
psmouse serio2: Failed to reset mouse on : -5
misc userio: Buffer overflowed, userio client isn't keeping up
==================================================================
BUG: KMSAN: uninit-value in synaptics_detect+0x1fa/0x2a0
drivers/input/mouse/synaptics.c:112
CPU: 1 PID: 41 Comm: kworker/1:2 Not tainted 4.19.0-rc1+ #42
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: events_long serio_handle_event
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x14b/0x190 lib/dump_stack.c:113
kmsan_report+0x183/0x2b0 mm/kmsan/kmsan.c:956
__msan_warning+0x70/0xc0 mm/kmsan/kmsan_instr.c:645
synaptics_detect+0x1fa/0x2a0 drivers/input/mouse/synaptics.c:112
psmouse_do_detect drivers/input/mouse/psmouse-base.c:1011 [inline]
psmouse_extensions+0x10fd/0x3820 drivers/input/mouse/psmouse-base.c:1106
psmouse_switch_protocol+0x184/0xd90 drivers/input/mouse/psmouse-base.c:1544
psmouse_connect+0x1387/0x2290 drivers/input/mouse/psmouse-base.c:1634
serio_connect_driver drivers/input/serio/serio.c:59 [inline]
serio_driver_probe+0xe3/0x150 drivers/input/serio/serio.c:790
really_probe+0x19ae/0x2040 drivers/base/dd.c:500
driver_probe_device+0x1b4/0x4f0 drivers/base/dd.c:662
__device_attach_driver+0x632/0x750 drivers/base/dd.c:758
bus_for_each_drv+0x27e/0x390 drivers/base/bus.c:461
__device_attach+0x381/0x5e0 drivers/base/dd.c:815
device_initial_probe+0x4a/0x60 drivers/base/dd.c:862
bus_probe_device+0x137/0x390 drivers/base/bus.c:521
device_add+0x2687/0x2c70 drivers/base/core.c:1927
serio_add_port drivers/input/serio/serio.c:554 [inline]
serio_handle_event+0x1d90/0x2700 drivers/input/serio/serio.c:222
process_one_work+0x1605/0x1f40 kernel/workqueue.c:2153
worker_thread+0x11a2/0x2590 kernel/workqueue.c:2296
kthread+0x465/0x4a0 kernel/kthread.c:247
ret_from_fork+0x35/0x40 arch/x86/entry/entry_64.S:416
Local variable description: ----param@synaptics_detect
Variable was created at:
synaptics_detect+0x50/0x2a0 drivers/input/mouse/synaptics.c:100
psmouse_do_detect drivers/input/mouse/psmouse-base.c:1011 [inline]
psmouse_extensions+0x10fd/0x3820 drivers/input/mouse/psmouse-base.c:1106
==================================================================
---
This bug 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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2018-09-20 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000f0575a057653dc12@google.com \
--to=syzbot+13cb3b01d0784e4ffc3f@syzkaller.appspotmail.com \
--cc=aaron.ma@canonical.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kt.liao@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@bitmath.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zhenjie.wang@sjtu.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).