From: syzbot <syzbot+listf1760c45c1a8a15cf5e1@syzkaller.appspotmail.com>
To: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly dri report (Apr 2025)
Date: Tue, 22 Apr 2025 05:41:29 -0700 [thread overview]
Message-ID: <68078e79.050a0220.8500a.0016.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, 1 new issues were detected and 0 were fixed.
In total, 18 issues are still open and 32 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3442 Yes WARNING in __alloc_frozen_pages_noprof
https://syzkaller.appspot.com/bug?extid=03fb58296859d8dbab4d
<2> 403 Yes WARNING in vkms_get_vblank_timestamp (2)
https://syzkaller.appspot.com/bug?extid=93bd128a383695391534
<3> 76 Yes WARNING in drm_wait_one_vblank (2)
https://syzkaller.appspot.com/bug?extid=147ba789658184f0ce04
<4> 75 No INFO: task hung in drm_atomic_get_plane_state
https://syzkaller.appspot.com/bug?extid=eee643fdccb7c015b3a6
<5> 72 Yes WARNING in drm_mode_create_lease_ioctl
https://syzkaller.appspot.com/bug?extid=6754751ad05524dae739
<6> 35 Yes KASAN: slab-use-after-free Read in drm_atomic_helper_wait_for_vblanks (2)
https://syzkaller.appspot.com/bug?extid=0f999d26a4fd79c3a23b
<7> 21 Yes WARNING in drm_gem_prime_fd_to_handle
https://syzkaller.appspot.com/bug?extid=268d319a7bfd92f4ae01
<8> 4 Yes WARNING in drm_prime_destroy_file_private (2)
https://syzkaller.appspot.com/bug?extid=59dcc2e7283a6f5f5ba1
<9> 3 Yes WARNING in drm_prime_fd_to_handle_ioctl
https://syzkaller.appspot.com/bug?extid=0da81ccba2345eeb7f48
<10> 1 No WARNING in virtio_gpu_queue_fenced_ctrl_buffer
https://syzkaller.appspot.com/bug?extid=5afbc12ca70811c2bffb
---
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:[~2025-04-22 12:41 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=68078e79.050a0220.8500a.0016.GAE@google.com \
--to=syzbot+listf1760c45c1a8a15cf5e1@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