From: Stephen Boyd <sboyd@codeaurora.org>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 14/38] clk: vt8500: fix sign of possible PLL values
Date: Thu, 1 Oct 2015 15:56:28 -0700 [thread overview]
Message-ID: <20151001225628.GU19319@codeaurora.org> (raw)
In-Reply-To: <1442842450-29769-15-git-send-email-a.hajda@samsung.com>
On 09/21, Andrzej Hajda wrote:
> With unsigned values underflow in loops can occur resulting in
> theoretically infinite loops.
>
> The problem has been detected using proposed semantic patch
> scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1].
>
> [1]: http://permalink.gmane.org/gmane.linux.kernel/2038576
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/clk/clk-vt8500.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/clk-vt8500.c b/drivers/clk/clk-vt8500.c
> index 37e9288..098e9fa 100644
> --- a/drivers/clk/clk-vt8500.c
> +++ b/drivers/clk/clk-vt8500.c
> @@ -384,7 +384,7 @@ static void vt8500_find_pll_bits(unsigned long rate, unsigned long parent_rate,
> static void wm8650_find_pll_bits(unsigned long rate, unsigned long parent_rate,
> u32 *multiplier, u32 *divisor1, u32 *divisor2)
> {
> - u32 mul, div1, div2;
> + int mul, div1, div2;
Only div2 seems to need the treatment here.
> u32 best_mul, best_div1, best_div2;
> unsigned long tclk, rate_err, best_err;
>
> @@ -452,7 +452,7 @@ static u32 wm8750_get_filter(u32 parent_rate, u32 divisor1)
> static void wm8750_find_pll_bits(unsigned long rate, unsigned long parent_rate,
> u32 *filter, u32 *multiplier, u32 *divisor1, u32 *divisor2)
> {
> - u32 mul, div1, div2;
> + int mul, div1, div2;
And here div1 and div2 are the only ones.
> u32 best_mul, best_div1, best_div2;
> unsigned long tclk, rate_err, best_err;
>
> @@ -496,7 +496,7 @@ static void wm8750_find_pll_bits(unsigned long rate, unsigned long parent_rate,
> static void wm8850_find_pll_bits(unsigned long rate, unsigned long parent_rate,
> u32 *multiplier, u32 *divisor1, u32 *divisor2)
> {
> - u32 mul, div1, div2;
> + int mul, div1, div2;
And div1 and div2 here.
Can we focus the changes on the actual problematic variables? I
suppose this has never mattered because we break out of these
loops.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-01 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 13:33 [PATCH 00/38] Fixes related to incorrect usage of unsigned types Andrzej Hajda
2015-09-21 13:33 ` [PATCH 14/38] clk: vt8500: fix sign of possible PLL values Andrzej Hajda
2015-10-01 22:56 ` Stephen Boyd [this message]
2015-10-02 4:49 ` [PATCH v2 " Andrzej Hajda
2015-12-14 10:30 ` Andrzej Hajda
2016-01-05 14:24 ` Andrzej Hajda
2016-01-30 0:44 ` Stephen Boyd
2015-09-21 13:42 ` [PATCH 00/38] Fixes related to incorrect usage of unsigned types David Howells
2015-09-22 9:13 ` Andrzej Hajda
2015-09-22 9:46 ` Jacek Anaszewski
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=20151001225628.GU19319@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.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).