From: syzbot <syzbot+listeb8d66e6043d7c79c774@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Jul 2024)
Date: Thu, 11 Jul 2024 00:30:26 -0700 [thread overview]
Message-ID: <0000000000008ea816061cf3bc76@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, 2 new issues were detected and 3 were fixed.
In total, 74 issues are still open and 343 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 870 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<2> 751 Yes INFO: task hung in uevent_show
https://syzkaller.appspot.com/bug?extid=edd9fe0d3a65b14588d5
<3> 700 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<4> 646 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
<5> 498 Yes INFO: rcu detected stall in hub_event
https://syzkaller.appspot.com/bug?extid=ec5f884c4a135aa0dbb9
<6> 483 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
<7> 409 Yes INFO: task hung in r871xu_dev_remove
https://syzkaller.appspot.com/bug?extid=f39c1dad0b7db49ca4a8
<8> 377 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
<9> 304 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<10> 243 Yes INFO: rcu detected stall in addrconf_rs_timer (6)
https://syzkaller.appspot.com/bug?extid=fecf8bd19c1f78edb255
---
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-07-11 7:30 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=0000000000008ea816061cf3bc76@google.com \
--to=syzbot+listeb8d66e6043d7c79c774@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.