From: syzbot <syzbot+lista02f0bac45ff1b3f6031@syzkaller.appspotmail.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly dri report (Nov 2024)
Date: Thu, 14 Nov 2024 00:59:22 -0800 [thread overview]
Message-ID: <6735bbea.050a0220.2a2fcc.0065.GAE@google.com> (raw)
Hello dri maintainers/developers,
This is a 31-day syzbot report for the dri subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/dri
During the period, 0 new issues were detected and 0 were fixed.
In total, 16 issues are still open and 31 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 841 Yes WARNING in drm_syncobj_array_find
https://syzkaller.appspot.com/bug?extid=95416f957d84e858b377
<2> 318 Yes WARNING in vkms_get_vblank_timestamp (2)
https://syzkaller.appspot.com/bug?extid=93bd128a383695391534
<3> 68 Yes WARNING in drm_mode_create_lease_ioctl
https://syzkaller.appspot.com/bug?extid=6754751ad05524dae739
<4> 62 No INFO: task hung in drm_atomic_get_plane_state
https://syzkaller.appspot.com/bug?extid=eee643fdccb7c015b3a6
<5> 28 Yes WARNING in drm_wait_one_vblank (2)
https://syzkaller.appspot.com/bug?extid=147ba789658184f0ce04
<6> 18 Yes WARNING in drm_gem_prime_fd_to_handle
https://syzkaller.appspot.com/bug?extid=268d319a7bfd92f4ae01
<7> 12 Yes divide error in drm_mode_vrefresh
https://syzkaller.appspot.com/bug?extid=622bba18029bcde672e1
<8> 4 Yes KASAN: slab-use-after-free Read in drm_atomic_helper_wait_for_vblanks (2)
https://syzkaller.appspot.com/bug?extid=0f999d26a4fd79c3a23b
<9> 4 Yes WARNING in drm_gem_object_handle_put_unlocked
https://syzkaller.appspot.com/bug?extid=ef3256a360c02207a4cb
<10> 3 Yes WARNING in drm_prime_fd_to_handle_ioctl
https://syzkaller.appspot.com/bug?extid=0da81ccba2345eeb7f48
---
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-11-14 8:59 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=6735bbea.050a0220.2a2fcc.0065.GAE@google.com \
--to=syzbot+lista02f0bac45ff1b3f6031@syzkaller.appspotmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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