linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: lenb@kernel.org, khilman@ti.com, deepthi@linux.vnet.ibm.com,
	g.trinabh@gmail.com, arjan@infradead.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	amit.kucheria@linaro.org
Subject: Re: [PATCH] cpuidle: Avoid possible NULL pointer dereference in __cpuidle_register_device()
Date: Tue, 03 Apr 2012 17:21:11 +0530	[thread overview]
Message-ID: <4F7AE42F.9080800@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F79FE8F.1040708@linaro.org>

On 04/03/2012 01:01 AM, Daniel Lezcano wrote:

> On 04/02/2012 04:44 PM, Srivatsa S. Bhat wrote:
>> In __cpuidle_register_device(), "dev->cpu" is used before checking if
>> dev is
>> non-NULL. Fix it.
>>
>> Signed-off-by: Srivatsa S. Bhat<srivatsa.bhat@linux.vnet.ibm.com>
>> ---
> 
> That should be fixed at the caller level. Usually, static function does
> not check the function parameters, it is up to the exported function to
> do that. It is supposed the static functions are called with valid
> parameters.
> 


Ok, good point! I hadn't thought about that.. I just happened to notice
that in __cpuidle_register_device(), the dev == NULL check is performed
_after_ dereferencing it, which made the check useless. So I tried to
fix that within that function. But thanks for pointing out the semantics..

> There are two callers for __cpuidle_register_device:
>  * cpuidle_register_device
>  * cpuidle_enable_device
> 
> Both of them do not check 'dev' is a valid parameter. They should as
> they are exported and could be used by an external module. IMHO, BUG_ON
> could be used here if dev == NULL.
>


BUG_ON? That would crash the system.. which might be unnecessary..

How about checking if dev == NULL in the 2 callers like you suggested 
and returning -EINVAL if dev is indeed NULL?

(And of course no checks for dev == NULL in __cpuidle_register_device).

 
> 
>>   drivers/cpuidle/cpuidle.c |    3 ++-
>>   1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
>> index 87411ce..75b381e 100644
>> --- a/drivers/cpuidle/cpuidle.c
>> +++ b/drivers/cpuidle/cpuidle.c
>> @@ -372,7 +372,7 @@ EXPORT_SYMBOL_GPL(cpuidle_disable_device);
>>   static int __cpuidle_register_device(struct cpuidle_device *dev)
>>   {
>>       int ret;
>> -    struct device *cpu_dev = get_cpu_device((unsigned long)dev->cpu);
>> +    struct device *cpu_dev;
>>       struct cpuidle_driver *cpuidle_driver = cpuidle_get_driver();
>>
>>       if (!dev)
>> @@ -380,6 +380,7 @@ static int __cpuidle_register_device(struct
>> cpuidle_device *dev)
>>       if (!try_module_get(cpuidle_driver->owner))
>>           return -EINVAL;
>>
>> +    cpu_dev = get_cpu_device((unsigned long)dev->cpu);
>>       init_completion(&dev->kobj_unregister);
>>
>>       per_cpu(cpuidle_devices, dev->cpu) = dev;
>>
> 
> 


Thank you for the review!

Regards,
Srivatsa S. Bhat


  reply	other threads:[~2012-04-03 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 14:44 [PATCH] cpuidle: Avoid possible NULL pointer dereference in __cpuidle_register_device() Srivatsa S. Bhat
2012-04-02 19:31 ` Daniel Lezcano
2012-04-03 11:51   ` Srivatsa S. Bhat [this message]
2012-04-03 12:08     ` Daniel Lezcano
2012-04-03 13:15       ` Srivatsa S. Bhat
2012-04-03 13:51         ` Daniel Lezcano
2012-04-03 14:04           ` Srivatsa S. Bhat
2012-04-03 14:17             ` Daniel Lezcano

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=4F7AE42F.9080800@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=amit.kucheria@linaro.org \
    --cc=arjan@infradead.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=g.trinabh@gmail.com \
    --cc=khilman@ti.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.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).