From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: linux-pm@vger.kernel.org, evgreen@chromium.org,
daidavid1@codeaurora.org, okukatla@codeaurora.org,
jcrouse@codeaurora.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] interconnect: Check for valid path in icc_set_bw()
Date: Fri, 20 Dec 2019 11:04:26 -0800 [thread overview]
Message-ID: <20191220190426.GE549437@yoga> (raw)
In-Reply-To: <20191220171310.24169-1-georgi.djakov@linaro.org>
On Fri 20 Dec 09:13 PST 2019, Georgi Djakov wrote:
> Use IS_ERR() to ensure that the path passed to icc_set_bw() is valid.
>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> ---
> drivers/interconnect/core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c
> index 63c164264b73..14a6f7ade44a 100644
> --- a/drivers/interconnect/core.c
> +++ b/drivers/interconnect/core.c
> @@ -498,6 +498,11 @@ int icc_set_bw(struct icc_path *path, u32 avg_bw, u32 peak_bw)
> if (!path || !path->num_nodes)
> return 0;
>
> + if (IS_ERR(path)) {
This is a sign of a logical error, and the print is likely to be
ignored/lost in the noise. So I think the response should aid to help
the developer hitting this to resolve the issue.
So I think this is more visible and more useful as:
if (WARN_ON(IS_ERR(path)))
return -EINVAL;
PS. Doesn't path->num_nodes == 0 fall in this category as well? When
would you have a path object with no nodes passed to this function?
Regards,
Bjorn
> + pr_err("%s: invalid path=%ld\n", __func__, PTR_ERR(path));
> + return -EINVAL;
> + }
> +
> mutex_lock(&icc_lock);
>
> old_avg = path->reqs[0].avg_bw;
next prev parent reply other threads:[~2019-12-20 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 17:13 [PATCH] interconnect: Check for valid path in icc_set_bw() Georgi Djakov
2019-12-20 19:04 ` Bjorn Andersson [this message]
2019-12-21 2:43 ` Georgi Djakov
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=20191220190426.GE549437@yoga \
--to=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=okukatla@codeaurora.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