mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corentin LABBE <clabbe.montjoie@gmail.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: p.zabel@pengutronix.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] gpu: ipu-v3: fix a possible NULL dereference
Date: Tue, 23 Aug 2016 18:23:30 +0200	[thread overview]
Message-ID: <45288b3c-76a2-f9ae-67ae-7dd49785e75b@gmail.com> (raw)
In-Reply-To: <CAOw6vbK=Y6JPVQKCE55RtzeE=A8Tgw8v+zdbuYQHwcuW5yQ3QQ@mail.gmail.com>

On 23/08/2016 17:24, Sean Paul wrote:
> On Tue, Aug 16, 2016 at 9:33 AM, LABBE Corentin
> <clabbe.montjoie@gmail.com> wrote:
>> of_match_device could return NULL, and so cause a NULL pointer
>> dereference later.
>>
>> For fixing this problem, we use of_device_get_match_data(), this will
>> simplify the code a little by using a standard function for
>> getting the match data.
>>
>> Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
>> ---
>>  drivers/gpu/ipu-v3/ipu-common.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/ipu-v3/ipu-common.c b/drivers/gpu/ipu-v3/ipu-common.c
>> index 99dcacf..05a9cc6 100644
>> --- a/drivers/gpu/ipu-v3/ipu-common.c
>> +++ b/drivers/gpu/ipu-v3/ipu-common.c
>> @@ -1207,15 +1207,13 @@ EXPORT_SYMBOL_GPL(ipu_dump);
>>
>>  static int ipu_probe(struct platform_device *pdev)
>>  {
>> -       const struct of_device_id *of_id =
>> -                       of_match_device(imx_ipu_dt_ids, &pdev->dev);
>>         struct ipu_soc *ipu;
>>         struct resource *res;
>>         unsigned long ipu_base;
>>         int i, ret, irq_sync, irq_err;
>>         const struct ipu_devtype *devtype;
>>
>> -       devtype = of_id->data;
>> +       devtype = of_device_get_match_data(&pdev->dev);
> 
> While you avoid the of_id dereference, it's possible that
> of_device_get_match_data() returns NULL, so you're really just moving
> the oops around.
> 
> Sean
> 

Hello

I apologize for didnt seen that, I will send an updated patch which fix that.

Regards

      reply	other threads:[~2016-08-23 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 13:33 LABBE Corentin
2016-08-23 15:24 ` Sean Paul
2016-08-23 16:23   ` Corentin LABBE [this message]

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=45288b3c-76a2-f9ae-67ae-7dd49785e75b@gmail.com \
    --to=clabbe.montjoie@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=seanpaul@chromium.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

all inboxes | Powered by JetHome®