From: syzbot <syzbot+4dd880c1184280378821@syzkaller.appspotmail.com>
To: dmitry.torokhov@gmail.com, glider@google.com,
greg.iforce@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] KMSAN: uninit-value in iforce_init_device (2)
Date: Mon, 07 Nov 2022 01:43:41 -0800 [thread overview]
Message-ID: <0000000000003adfa805ecde42f8@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 968c2729e576 x86: kmsan: fix comment in kmsan_shadow.c
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14efb852880000
kernel config: https://syzkaller.appspot.com/x/.config?x=131312b26465c190
dashboard link: https://syzkaller.appspot.com/bug?extid=4dd880c1184280378821
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project.git 610139d2d9ce6746b3c617fb3e2f7886272d26ff), GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/56b19fc61d98/disk-968c2729.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b048b309a6e5/vmlinux-968c2729.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4dd880c1184280378821@syzkaller.appspotmail.com
iforce 1-1:0.0: usb_submit_urb failed: -71
iforce 1-1:0.0: usb_submit_urb failed: -71
iforce 1-1:0.0: usb_submit_urb failed: -71
=====================================================
BUG: KMSAN: uninit-value in iforce_init_device+0x1bd5/0x2010 drivers/input/joystick/iforce/iforce-main.c:297
iforce_init_device+0x1bd5/0x2010 drivers/input/joystick/iforce/iforce-main.c:297
iforce_usb_probe+0xc86/0x11c0 drivers/input/joystick/iforce/iforce-usb.c:238
usb_probe_interface+0xc4b/0x11f0 drivers/usb/core/driver.c:396
really_probe+0x506/0x1000 drivers/base/dd.c:639
__driver_probe_device+0x2fa/0x3d0 drivers/base/dd.c:778
driver_probe_device+0x72/0x7a0 drivers/base/dd.c:808
__device_attach_driver+0x548/0x8e0 drivers/base/dd.c:936
bus_for_each_drv+0x1fc/0x360 drivers/base/bus.c:427
__device_attach+0x42a/0x720 drivers/base/dd.c:1008
device_initial_probe+0x2e/0x40 drivers/base/dd.c:1057
bus_probe_device+0x13c/0x3b0 drivers/base/bus.c:487
device_add+0x1d4b/0x26c0 drivers/base/core.c:3517
usb_set_configuration+0x30f8/0x37e0 drivers/usb/core/message.c:2170
usb_generic_driver_probe+0x105/0x290 drivers/usb/core/generic.c:238
usb_probe_device+0x288/0x490 drivers/usb/core/driver.c:293
really_probe+0x506/0x1000 drivers/base/dd.c:639
__driver_probe_device+0x2fa/0x3d0 drivers/base/dd.c:778
driver_probe_device+0x72/0x7a0 drivers/base/dd.c:808
__device_attach_driver+0x548/0x8e0 drivers/base/dd.c:936
bus_for_each_drv+0x1fc/0x360 drivers/base/bus.c:427
__device_attach+0x42a/0x720 drivers/base/dd.c:1008
device_initial_probe+0x2e/0x40 drivers/base/dd.c:1057
bus_probe_device+0x13c/0x3b0 drivers/base/bus.c:487
device_add+0x1d4b/0x26c0 drivers/base/core.c:3517
usb_new_device+0x17ac/0x2370 drivers/usb/core/hub.c:2573
hub_port_connect drivers/usb/core/hub.c:5353 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5497 [inline]
port_event drivers/usb/core/hub.c:5653 [inline]
hub_event+0x5589/0x8080 drivers/usb/core/hub.c:5735
process_one_work+0xb27/0x13e0 kernel/workqueue.c:2289
worker_thread+0x1076/0x1d60 kernel/workqueue.c:2436
kthread+0x31b/0x430 kernel/kthread.c:376
ret_from_fork+0x1f/0x30
Local variable buf created at:
iforce_init_device+0x5a/0x2010 drivers/input/joystick/iforce/iforce-main.c:217
iforce_usb_probe+0xc86/0x11c0 drivers/input/joystick/iforce/iforce-usb.c:238
CPU: 0 PID: 15409 Comm: kworker/0:2 Not tainted 6.0.0-rc5-syzkaller-48543-g968c2729e576 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: usb_hub_wq hub_event
=====================================================
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2022-11-07 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 9:43 syzbot [this message]
2022-11-07 10:47 ` [PATCH] Input: iforce - invert valid length check when fetching device IDs Tetsuo Handa
2022-11-07 18:29 ` Dmitry Torokhov
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=0000000000003adfa805ecde42f8@google.com \
--to=syzbot+4dd880c1184280378821@syzkaller.appspotmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=glider@google.com \
--cc=greg.iforce@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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).