From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: lenb@kernel.org
Cc: 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,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
daniel.lezcano@linaro.org, amit.kucheria@linaro.org
Subject: [PATCH] cpuidle: Avoid possible NULL pointer dereference in __cpuidle_register_device()
Date: Mon, 02 Apr 2012 20:14:22 +0530 [thread overview]
Message-ID: <20120402144422.11574.83174.stgit@srivatsabhat.in.ibm.com> (raw)
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>
---
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;
next reply other threads:[~2012-04-02 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 14:44 Srivatsa S. Bhat [this message]
2012-04-02 19:31 ` [PATCH] cpuidle: Avoid possible NULL pointer dereference in __cpuidle_register_device() Daniel Lezcano
2012-04-03 11:51 ` Srivatsa S. Bhat
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=20120402144422.11574.83174.stgit@srivatsabhat.in.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).