From: syzbot <syzbot+list7326d21fc77552823fb4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Aug 2023)
Date: Wed, 02 Aug 2023 04:18:58 -0700 [thread overview]
Message-ID: <00000000000076ffa30601eed47b@google.com> (raw)
Hello usb maintainers/developers,
This is a 31-day syzbot report for the usb subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/usb
During the period, 4 new issues were detected and 3 were fixed.
In total, 73 issues are still open and 322 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2254 Yes KMSAN: uninit-value in mii_nway_restart
https://syzkaller.appspot.com/bug?extid=1f53a30781af65d2c955
<2> 2098 Yes WARNING in firmware_fallback_sysfs
https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
<3> 1059 Yes KMSAN: uninit-value in alauda_check_media
https://syzkaller.appspot.com/bug?extid=e7d46eb426883fb97efd
<4> 983 Yes WARNING in smsusb_term_device
https://syzkaller.appspot.com/bug?extid=40ac6e73326e79ee8ecb
<5> 851 Yes INFO: task hung in usb_get_descriptor (2)
https://syzkaller.appspot.com/bug?extid=e8db9d9e65feff8fa471
<6> 485 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
<7> 355 Yes KASAN: slab-use-after-free Read in pvr2_context_set_notify
https://syzkaller.appspot.com/bug?extid=621409285c4156a009b3
<8> 340 Yes INFO: task hung in r871xu_dev_remove
https://syzkaller.appspot.com/bug?extid=f39c1dad0b7db49ca4a8
<9> 325 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<10> 238 Yes INFO: task hung in netdev_run_todo (2)
https://syzkaller.appspot.com/bug?extid=9d77543f47951a63d5c1
---
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.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2023-08-02 11:19 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=00000000000076ffa30601eed47b@google.com \
--to=syzbot+list7326d21fc77552823fb4@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.