From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel Fu <danifu@nvidia.com>
Cc: daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, joqiu@nvidia.com
Subject: Re: [PATCH] cpuidle: Check cpuidle driver before add refcount
Date: Fri, 30 Aug 2013 14:01:02 +0200 [thread overview]
Message-ID: <2041584.4YznqfT0Od@vostro.rjw.lan> (raw)
In-Reply-To: <1377863302-22465-1-git-send-email-danifu@nvidia.com>
On Friday, August 30, 2013 07:48:22 PM Daniel Fu wrote:
> If the current CPU has no cpuidle driver, drv will be NULL.
> Check if we get drv successfully before add refount
> to prevent Kernel panic.
What is the actual scenario that may lead to this panic?
Rafael
> Signed-off-by: Daniel Fu <danifu@nvidia.com>
> ---
> drivers/cpuidle/driver.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
> index 3ac499d..6e11701 100644
> --- a/drivers/cpuidle/driver.c
> +++ b/drivers/cpuidle/driver.c
> @@ -331,7 +331,8 @@ struct cpuidle_driver *cpuidle_driver_ref(void)
> spin_lock(&cpuidle_driver_lock);
>
> drv = cpuidle_get_driver();
> - drv->refcnt++;
> + if (drv)
> + drv->refcnt++;
>
> spin_unlock(&cpuidle_driver_lock);
> return drv;
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-08-30 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 11:48 [PATCH] cpuidle: Check cpuidle driver before add refcount Daniel Fu
2013-08-30 12:01 ` Rafael J. Wysocki [this message]
2013-08-30 12:26 ` Daniel Fu
2013-08-30 13:25 ` Rafael J. Wysocki
2013-08-30 13:39 ` Daniel Fu
2013-08-30 19:51 ` Rafael J. Wysocki
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=2041584.4YznqfT0Od@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=daniel.lezcano@linaro.org \
--cc=danifu@nvidia.com \
--cc=joqiu@nvidia.com \
--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