From: syzbot <syzbot+list70ae5dd68c735d914e1e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report
Date: Thu, 30 Mar 2023 02:59:55 -0700 [thread overview]
Message-ID: <00000000000093abe005f81b27be@google.com> (raw)
Hello media maintainers/developers,
This is a 30-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, 18 issues are still open and 81 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
2180 Yes KMSAN: uninit-value in dib3000mb_attach (2)
https://syzkaller.appspot.com/bug?extid=c88fc0ebe0d5935c70da
705 Yes WARNING in get_vaddr_frames
https://syzkaller.appspot.com/bug?extid=59a71007ccac79e8bb69
333 Yes WARNING in smsusb_term_device
https://syzkaller.appspot.com/bug?extid=40ac6e73326e79ee8ecb
90 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
87 Yes WARNING in media_create_pad_link
https://syzkaller.appspot.com/bug?extid=dd320d114deb3f5bb79b
31 Yes inconsistent lock state in sync_info_debugfs_show
https://syzkaller.appspot.com/bug?extid=007bfe0f3330f6e1e7d1
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.
reply other threads:[~2023-03-30 10:00 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=00000000000093abe005f81b27be@google.com \
--to=syzbot+list70ae5dd68c735d914e1e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox