From: syzbot <syzbot+listd2a1ebc22715cc638b5a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Jan 2024)
Date: Fri, 05 Jan 2024 05:17:24 -0800 [thread overview]
Message-ID: <00000000000043127b060e32ab2a@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, 0 new issues were detected and 0 were fixed.
In total, 62 issues are still open and 331 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2979 Yes WARNING in firmware_fallback_sysfs
https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
<2> 2797 Yes KMSAN: uninit-value in dib3000mb_attach (2)
https://syzkaller.appspot.com/bug?extid=c88fc0ebe0d5935c70da
<3> 832 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<4> 548 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
<5> 429 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<6> 385 Yes INFO: task hung in r871xu_dev_remove
https://syzkaller.appspot.com/bug?extid=f39c1dad0b7db49ca4a8
<7> 304 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<8> 240 No INFO: task hung in hub_event (3)
https://syzkaller.appspot.com/bug?extid=a7edecbf389d11a369d4
<9> 239 Yes INFO: task hung in netdev_run_todo (2)
https://syzkaller.appspot.com/bug?extid=9d77543f47951a63d5c1
<10> 216 Yes INFO: rcu detected stall in hub_event
https://syzkaller.appspot.com/bug?extid=ec5f884c4a135aa0dbb9
---
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:[~2024-01-05 13:17 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=00000000000043127b060e32ab2a@google.com \
--to=syzbot+listd2a1ebc22715cc638b5a@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.