From: syzbot <syzbot+list11d35df624b178fd7375@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (May 2023)
Date: Wed, 31 May 2023 05:40:02 -0700 [thread overview]
Message-ID: <000000000000652f7405fcfc9e79@google.com> (raw)
Hello media maintainers/developers,
This is a 31-day syzbot report for the media subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/media
During the period, 0 new issues were detected and 0 were fixed.
In total, 17 issues are still open and 83 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2373 Yes KMSAN: uninit-value in dib3000mb_attach (2)
https://syzkaller.appspot.com/bug?extid=c88fc0ebe0d5935c70da
<2> 1161 Yes WARNING in get_vaddr_frames
https://syzkaller.appspot.com/bug?extid=59a71007ccac79e8bb69
<3> 653 Yes WARNING in smsusb_term_device
https://syzkaller.appspot.com/bug?extid=40ac6e73326e79ee8ecb
<4> 140 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<5> 87 Yes WARNING in media_create_pad_link
https://syzkaller.appspot.com/bug?extid=dd320d114deb3f5bb79b
<6> 1 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
---
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-05-31 12:40 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=000000000000652f7405fcfc9e79@google.com \
--to=syzbot+list11d35df624b178fd7375@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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.