dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216338] New: Null Pointer Dereference in rockchip_drm_vop2.c
Date: Mon, 08 Aug 2022 14:40:01 +0000	[thread overview]
Message-ID: <bug-216338-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216338

            Bug ID: 216338
           Summary: Null Pointer Dereference in rockchip_drm_vop2.c
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.19.0
          Hardware: ARM
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: macromorgan@hotmail.com
        Regression: No

When you use more than 1 video port (VP0 and VP1, for instance) on a Rockchip
RK3566 with the VOP2 driver, the driver issues a null pointer dereference when
it gets to the drm_crtc_init_with_planes function here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c?h=v5.19#n2333

This appears to be because the function above it assigns primary planes to all
active video ports, but since it has special logic for the RK3566 it only ends
up with 1 primary plane to assign to a video port. When it encounters a second
video port it assigns it nothing, and then triggers a null pointer dereference
when it gets to the drm_crtc_init_with_planes function because plane is null.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2022-08-08 14:55 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=bug-216338-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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;
as well as URLs for NNTP newsgroup(s).