From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
rui.zhang@intel.com, edubezval@gmail.com
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
dan.carpenter@oracle.com, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V2 3/5] thermal: devfreq: Check OPP for errors
Date: Tue, 7 Feb 2017 09:40:03 +0530 [thread overview]
Message-ID: <06c4a7a43d537bf078f6ac72187853e11bd0384e.1486440448.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <79611a51240c83504c35a8739fe8e1837e903671.1486440448.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1486440448.git.viresh.kumar@linaro.org>
It is possible for dev_pm_opp_find_freq_exact() to return errors. It was
all fine earlier as dev_pm_opp_get_voltage() had a check within it to
check for invalid OPPs, but dev_pm_opp_put() doesn't have any similar
checks and the callers need to make sure OPP is valid before calling
them.
Also update the later dev_warn_ratelimited() to not print the error
message as the OPP is guaranteed to be valid now.
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/thermal/devfreq_cooling.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/devfreq_cooling.c b/drivers/thermal/devfreq_cooling.c
index 218ccc30c7ad..74d4846c66cd 100644
--- a/drivers/thermal/devfreq_cooling.c
+++ b/drivers/thermal/devfreq_cooling.c
@@ -225,13 +225,19 @@ get_static_power(struct devfreq_cooling_device *dfc, unsigned long freq)
if (PTR_ERR(opp) == -ERANGE)
opp = dev_pm_opp_find_freq_exact(dev, freq, false);
+ if (IS_ERR(opp)) {
+ dev_err_ratelimited(dev, "Failed to find OPP for frequency %lu: %ld\n",
+ freq, PTR_ERR(opp));
+ return 0;
+ }
+
voltage = dev_pm_opp_get_voltage(opp) / 1000; /* mV */
dev_pm_opp_put(opp);
if (voltage == 0) {
dev_err_ratelimited(dev,
- "Failed to get voltage for frequency %lu: %ld\n",
- freq, IS_ERR(opp) ? PTR_ERR(opp) : 0);
+ "Failed to get voltage for frequency %lu\n",
+ freq);
return 0;
}
--
2.7.1.410.g6faf27b
next prev parent reply other threads:[~2017-02-07 4:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 4:09 [PATCH V2 0/5] thermal: minor cleanup/fixes Viresh Kumar
2017-02-07 4:10 ` [PATCH V2 1/5] thermal: devfreq: Simplify expression Viresh Kumar
2017-02-07 4:10 ` [PATCH V2 2/5] thermal: devfreq_cooling: Replace dev_warn with dev_err Viresh Kumar
2017-02-07 4:10 ` Viresh Kumar [this message]
2017-02-07 4:10 ` [PATCH V2 4/5] thermal: cpu_cooling: " Viresh Kumar
2017-02-07 4:10 ` [PATCH V2 5/5] thermal: cpu_cooling: Check OPP for errors Viresh Kumar
2017-02-20 10:29 ` [PATCH V2 0/5] thermal: minor cleanup/fixes Viresh Kumar
2017-02-21 6:30 ` Zhang Rui
2017-02-24 8:49 ` Viresh Kumar
2017-03-08 4:24 ` Viresh Kumar
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=06c4a7a43d537bf078f6ac72187853e11bd0384e.1486440448.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=dan.carpenter@oracle.com \
--cc=edubezval@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@linaro.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).