From: Stefan Agner <stefan@agner.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Meng Yi <meng.yi@nxp.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RESEND,V2] drm: fsl-dcu: Fix no fb check bug
Date: Wed, 13 Jan 2016 21:54:09 -0800 [thread overview]
Message-ID: <9fbe6c7162f0ae5d39c66ae373bc294d@agner.ch> (raw)
In-Reply-To: <CACvgo509CWAwN=WLxdP1-wU1UeyjPGZXrZkqh9y9Lwzi4C1RrA@mail.gmail.com>
On 2016-01-08 01:20, Emil Velikov wrote:
> Hi guys,
>
> Am I loosing the plot here or something feels amiss here ?
>
> On 6 January 2016 at 06:12, Meng Yi <meng.yi@nxp.com> wrote:
>> For state->fb or state->crtc may be NULL in fsl_dcu_drm_plane_atomic_check
>> function, if so, return 0.
>>
>> Signed-off-by: Meng Yi <meng.yi@nxp.com>
>> Signed-off-by: Jianwei Wang <jianwei.wang.chn@gmail.com>
>>
>> ---
>>
>> change in v2:
>> -Add state->crtc check
>> -return 0 when state->fb or state->crtc is NULL, instead of -EINVAL
>> Adviced by Daniel Stone
>>
>> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c
>> index 4b13cf9..8965580 100644
>> --- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c
>> +++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c
>> @@ -41,6 +41,9 @@ static int fsl_dcu_drm_plane_atomic_check(struct drm_plane *plane,
>> {
>> struct drm_framebuffer *fb = state->fb;
>>
>> + if (!state->fb || !state->crtc)
>> + return 0;
>> +
> Namely: if we return success here core drm will end up calling the
> atomic_update...
>
After atomic_check atomic_disable could be called too. However, this
seem not directly depend on state'>fb, but more on plane->state->crtc.
>> switch (fb->pixel_format) {
>> case DRM_FORMAT_RGB565:
>> case DRM_FORMAT_RGB888:
>> @@ -85,9 +88,6 @@ static void fsl_dcu_drm_plane_atomic_update(struct drm_plane *plane,
>> unsigned int alpha, bpp;
>> int index, ret;
>>
>> - if (!fb)
>> - return;
>> -
> ... which no longer has the !fb check, and we'll crash with null deref
> a few lines below ?
If there is a legitimate situation where fb is null which also
ultimately leads to a atomic_commit, I guess we should keep the return
here...
--
Stefan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-14 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 4:12 [RESEND,V2] drm: fsl-dcu: Fix no fb check bug Meng Yi
2016-01-08 9:20 ` Emil Velikov
2016-01-14 5:54 ` Stefan Agner [this message]
2016-01-14 8:23 ` Meng Yi
2016-01-26 21:18 ` Emil Velikov
2016-01-28 2:23 ` Stefan Agner
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=9fbe6c7162f0ae5d39c66ae373bc294d@agner.ch \
--to=stefan@agner.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=meng.yi@nxp.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;
as well as URLs for NNTP newsgroup(s).