linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Grygorii Strashko <Grygorii.Strashko@linaro.org>,
	Kevin Hilman <khilman@linaro.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / clock_ops: Fix clock error check in __pm_clk_add()
Date: Fri, 8 May 2015 10:19:55 -0700	[thread overview]
Message-ID: <20150508171955.GA38039@dtor-ws> (raw)
In-Reply-To: <1431074863-19124-1-git-send-email-geert+renesas@glider.be>

On Fri, May 08, 2015 at 10:47:43AM +0200, Geert Uytterhoeven wrote:
> In the final iteration of commit 245bd6f6af8a62a2 ("PM / clock_ops: Add
> pm_clk_add_clk()"), a refcount increment was added by Grygorii Strashko.
> However, the accompanying IS_ERR() check operates on the wrong clock
> pointer, which is always zero at this point, i.e. not an error.
> This may lead to a NULL pointer dereference later, when __clk_get()
> tries to dereference an error pointer.
> 
> Check the passed clock pointer instead to fix this.

Frankly I would remove the check altogether. Why do we only check for
IS_ERR and not NULL or otherwise validate the pointer? The clk is passed
in and we do not call any API that would return ERR_PTR-encoded value to
us so we shoud lnot even try to handle IS_ERR here.

> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Fixes: 245bd6f6af8a62a2 ("PM / clock_ops: Add pm_clk_add_clk()")
> ---
> Note that there are no users of pm_clk_add_clk() in next-20150508, so
> for now no in-tree code is affected.
> ---
>  drivers/base/power/clock_ops.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/base/power/clock_ops.c b/drivers/base/power/clock_ops.c
> index 7fdd0172605afe1b..c7b0fcebf168cabe 100644
> --- a/drivers/base/power/clock_ops.c
> +++ b/drivers/base/power/clock_ops.c
> @@ -93,7 +93,7 @@ static int __pm_clk_add(struct device *dev, const char *con_id,
>  			return -ENOMEM;
>  		}
>  	} else {
> -		if (IS_ERR(ce->clk) || !__clk_get(clk)) {
> +		if (IS_ERR(clk) || !__clk_get(clk)) {
>  			kfree(ce);
>  			return -ENOENT;
>  		}
> -- 
> 1.9.1
> 

Thanks.

-- 
Dmitry

  reply	other threads:[~2015-05-08 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  8:47 [PATCH] PM / clock_ops: Fix clock error check in __pm_clk_add() Geert Uytterhoeven
2015-05-08 17:19 ` Dmitry Torokhov [this message]
2015-05-08 20:59   ` Geert Uytterhoeven
2015-05-08 21:05     ` Dmitry Torokhov
2015-05-12 13:55       ` Grygorii.Strashko@linaro.org
2015-05-12 16:42         ` Dmitry Torokhov
2015-05-12 17:59           ` Grygorii.Strashko@linaro.org
2015-05-12 18:07             ` Dmitry Torokhov
2015-05-13  0:22               ` Rafael J. Wysocki
2015-05-13  0:32                 ` Dmitry Torokhov
2015-05-13 22:45                   ` Rafael J. Wysocki
2015-05-16 21:37                     ` Geert Uytterhoeven
2015-05-18  0:22                       ` 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=20150508171955.GA38039@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=Grygorii.Strashko@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).