All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince Hsu <vinceh@nvidia.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v1] drm/nouveau/clk: avoid potential null-dereference
Date: Thu, 8 Jan 2015 14:02:31 +0800	[thread overview]
Message-ID: <54AE1D77.5010709@nvidia.com> (raw)
In-Reply-To: <CAKb7Uvj-DxQ6R89cdas0VcJgQeprEKXzZQ5ASZff6qZaVhHqHA@mail.gmail.com>


On 01/08/2015 01:52 PM, Ilia Mirkin wrote:
> On Thu, Jan 8, 2015 at 12:40 AM, Vince Hsu <vinceh@nvidia.com> wrote:
>> On 01/08/2015 12:57 PM, Ilia Mirkin wrote:
>>> On Wed, Jan 7, 2015 at 11:32 PM, Vince Hsu <vinceh@nvidia.com> wrote:
>>>> On 01/08/2015 10:45 AM, Ilia Mirkin wrote:
>>>>> On Wed, Jan 7, 2015 at 5:29 PM, Andy Shevchenko
>>>>> <andy.shevchenko@gmail.com> wrote:
>>>>>> We have to check pointer before usage.
>>>>>>
>>>>>> Reported-by: Andrey Karpov <karpov@viva64.com>
>>>>>> Signed-off-by: Andy Shevchenko <andy.shevchenko@gmail.com>
>>>>>> ---
>>>>>>     drivers/gpu/drm/nouveau/core/subdev/clock/base.c | 4 +++-
>>>>>>     1 file changed, 3 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/base.c
>>>>>> b/drivers/gpu/drm/nouveau/core/subdev/clock/base.c
>>>>>> index e51b72d..2e84436 100644
>>>>>> --- a/drivers/gpu/drm/nouveau/core/subdev/clock/base.c
>>>>>> +++ b/drivers/gpu/drm/nouveau/core/subdev/clock/base.c
>>>>>> @@ -322,7 +322,6 @@ nouveau_pstate_new(struct nouveau_clock *clk, int
>>>>>> idx)
>>>>>>                    return 0;
>>>>>>
>>>>>>            pstate = kzalloc(sizeof(*pstate), GFP_KERNEL);
>>>>>> -       cstate = &pstate->base;
>>>>> What's wrong with this line? If pstate == NULL, &pstate->base == NULL
>>>>> as well and we return.
>>>> If pstate == NULL (kzalloc returned NULL), pstate->base triggers a null
>>>> pointer
>>>> deference error?
>>> Where do you see "pstate->base"? I only see "&pstate->base" which
>>> merely computes an offset into a structure... No reason to dereference
>>> pstate.
>> Sorry that I don't quite understand. We do need deference pstate to get
>> the member base which has type nouveau_cstate, and then assign
>> the address of base to cstate for later use.
>>
>> struct nouveau_pstate {
>>      struct list_head head;
>>      struct list_head list; /* c-states */
>>      struct nouveau_cstate base;
>>      u8 pstate;
>>      u8 fanspeed;
>> };
> &pstate->base is the same thing as
>
> (void *)pstate + offsetof(struct nouveau_pstate, base)
>
> At no point is pstate dereferenced. In fact, take a look at
>
> http://en.wikipedia.org/wiki/Offsetof
>
> which says that the traditional implementation of offsetof is
>
> #define offsetof(st, m) ((size_t)(&((st *)0)->m))
>
Oh I got your point. You're absolutely right. Thanks for the patience. :)

Vince


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-01-08  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 22:29 [PATCH v1] drm/nouveau/clk: avoid potential null-dereference Andy Shevchenko
2015-01-08  2:45 ` Ilia Mirkin
2015-01-08  4:32   ` Vince Hsu
2015-01-08  4:57     ` Ilia Mirkin
2015-01-08  5:40       ` Vince Hsu
2015-01-08  5:52         ` Ilia Mirkin
2015-01-08  6:02           ` Vince Hsu [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=54AE1D77.5010709@nvidia.com \
    --to=vinceh@nvidia.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.