From: Javi Merino <javi.merino@arm.com>
To: "edubezval@gmail.com" <edubezval@gmail.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] thermal: cpu_cooling: Check memory allocation of power_table
Date: Wed, 25 Mar 2015 11:47:05 +0000 [thread overview]
Message-ID: <20150325114705.GB3125@e104805> (raw)
In-Reply-To: <1426875613-31612-1-git-send-email-javi.merino@arm.com>
On Fri, Mar 20, 2015 at 06:20:13PM +0000, Javi Merino wrote:
> We allocate the power_table in memory but we don't test whether the
> allocation succeeded. Return -ENOMEM if kcalloc() fails.
>
> Fixes: e0128d8ab423 ("thermal: cpu_cooling: implement the power cooling device API")
> Cc: Eduardo Valentin <edubezval@gmail.com>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Javi Merino <javi.merino@arm.com>
> ---
> This applies on top of the linus branch in Eduardo's repository
>
> drivers/thermal/cpu_cooling.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
> index c4974144c787..3a01dfd5b29c 100644
> --- a/drivers/thermal/cpu_cooling.c
> +++ b/drivers/thermal/cpu_cooling.c
> @@ -329,6 +329,10 @@ static int build_dyn_power_table(struct cpufreq_cooling_device *cpufreq_device,
> }
>
> power_table = kcalloc(num_opps, sizeof(*power_table), GFP_KERNEL);
> + if (!power_table) {
> + ret = -ENOMEM;
> + goto unlock;
> + }
>
> for (freq = 0, i = 0;
> opp = dev_pm_opp_find_freq_ceil(dev, &freq), !IS_ERR(opp);
> --
> 1.9.1
Gentle reminder. Cheers,
Javi
prev parent reply other threads:[~2015-03-25 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 18:20 [PATCH] thermal: cpu_cooling: Check memory allocation of power_table Javi Merino
2015-03-25 11:47 ` Javi Merino [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=20150325114705.GB3125@e104805 \
--to=javi.merino@arm.com \
--cc=edubezval@gmail.com \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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