From: Archit Taneja <architt@codeaurora.org>
To: robdclark@gmail.com, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/msm: Fix NULL deref in adreno_load_gpu
Date: Wed, 20 Dec 2017 12:18:21 +0530 [thread overview]
Message-ID: <47ac0981-5b3b-86b3-6fd8-77fa769b7c56@codeaurora.org> (raw)
In-Reply-To: <20171215153325.GA25601@jcrouse-lnx.qualcomm.com>
On 12/15/2017 09:03 PM, Jordan Crouse wrote:
> On Thu, Dec 14, 2017 at 11:11:50AM +0530, Archit Taneja wrote:
>> The msm/kms driver should work even if there is no GPU device specified
>> in DT. Currently, we get a NULL dereference crash in adreno_load_gpu
>> since the driver assumes that priv->gpu_pdev is non-NULL.
>>
>> Perform an additional check on priv->gpu_pdev before trying to retrieve
>> the msm_gpu pointer from it.
>>
>> Fixes: eec874ce5ff1 (drm/msm/adreno: load gpu at probe/bind time)
>>
>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>> ---
>> drivers/gpu/drm/msm/adreno/adreno_device.c | 11 +++++++++--
>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/adreno/adreno_device.c b/drivers/gpu/drm/msm/adreno/adreno_device.c
>> index 05022ea2a007..ac60cf3c794e 100644
>> --- a/drivers/gpu/drm/msm/adreno/adreno_device.c
>> +++ b/drivers/gpu/drm/msm/adreno/adreno_device.c
>> @@ -124,10 +124,17 @@ const struct adreno_info *adreno_info(struct adreno_rev rev)
>> struct msm_gpu *adreno_load_gpu(struct drm_device *dev)
>> {
>> struct msm_drm_private *priv = dev->dev_private;
>> - struct platform_device *pdev = priv->gpu_pdev;
>> - struct msm_gpu *gpu = platform_get_drvdata(priv->gpu_pdev);
>> + struct platform_device *pdev;
>> + struct msm_gpu *gpu;
>> int ret;
>>
>> + pdev = priv->gpu_pdev;
>> + if (!pdev) {
>> + dev_dbg(dev->dev, "no adreno platform device found\n");
>> + return NULL;
>> + }
>> +
>> + gpu = platform_get_drvdata(pdev);
>> if (!gpu) {
>> dev_err(dev->dev, "no adreno device\n");
>> return NULL;
>
> Obviously correct fix but I can't help but think that we should share the same
> error message, so something like:
>
> struct msm_gpu *gpu = NULL;
>
> ..
>
> if (priv->gpu_pdev)
> gpu = platform_get_drvdata(priv->gpu_pdev);
>
> if (!gpu) {
> dev_err(dev->dev, "No GPU device was was found\n");
> return NULL;
> }
>
> (also, I can't help but think maybe that dev_err should be a ONCE so you don't
> get a nasty message every time you open the file descriptor).
This approach looks better. I'll re-spin.
Thanks,
Archit
>
> Jordan
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-20 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 5:41 [PATCH] drm/msm: Fix NULL deref in adreno_load_gpu Archit Taneja
2017-12-15 15:33 ` Jordan Crouse
2017-12-20 6:48 ` Archit Taneja [this message]
2017-12-22 10:11 ` [PATCH v2] " Archit Taneja
2018-01-02 18:32 ` Jordan Crouse
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=47ac0981-5b3b-86b3-6fd8-77fa769b7c56@codeaurora.org \
--to=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.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