From: syzbot <syzbot+listf54da26a126f0ba232c7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (May 2024)
Date: Tue, 14 May 2024 13:49:34 -0700 [thread overview]
Message-ID: <000000000000afec080618702339@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, 18 issues are still open and 85 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 13266 Yes possible deadlock in v4l2_ctrl_handler_log_status
https://syzkaller.appspot.com/bug?extid=9948f8e188482c5d1a3e
<2> 870 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<3> 289 Yes inconsistent lock state in sync_timeline_debug_remove
https://syzkaller.appspot.com/bug?extid=7dcd254b8987a29f6450
<4> 101 Yes WARNING in media_create_pad_link
https://syzkaller.appspot.com/bug?extid=dd320d114deb3f5bb79b
<5> 11 No WARNING in call_s_stream
https://syzkaller.appspot.com/bug?extid=5bcd7c809d365e14c4df
---
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-05-14 20:49 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=000000000000afec080618702339@google.com \
--to=syzbot+listf54da26a126f0ba232c7@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