From: Larry Finger <Larry.Finger@lwfinger.net>
To: Rand Deeb <rand.sec96@gmail.com>, Michael Buesch <m@bues.ch>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: deeb.rand@confident.ru, lvc-project@linuxtesting.org,
voskresenski.stanislav@confident.ru
Subject: Re: [PATCH v2] ssb: Fix division by zero issue in ssb_calc_clock_rate
Date: Mon, 4 Sep 2023 19:59:03 -0500 [thread overview]
Message-ID: <96eb9ff2-a687-bbd5-9cb1-4b044f7deae3@lwfinger.net> (raw)
In-Reply-To: <20230904232346.34991-1-rand.sec96@gmail.com>
On 9/4/23 18:23, Rand Deeb wrote:
> In ssb_calc_clock_rate(), there is a potential issue where the value of
> m1 could be zero due to initialization using clkfactor_f6_resolv(). This
> situation raised concerns about the possibility of a division by zero
> error.
>
> We fixed it by following the suggestions provided by Larry Finger
> <Larry.Finger@lwfinger.net> and Michael Büsch <m@bues.ch>. The fix
> involves returning a value of 1 instead of 0 in clkfactor_f6_resolv().
> This modification ensures the proper functioning of the code and
> eliminates the risk of division by zero errors.
>
> Signed-off-by: Rand Deeb <rand.sec96@gmail.com>
> ---
> drivers/ssb/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ssb/main.c b/drivers/ssb/main.c
> index 0a26984acb2c..9e54bc7eec66 100644
> --- a/drivers/ssb/main.c
> +++ b/drivers/ssb/main.c
> @@ -835,7 +835,7 @@ static u32 clkfactor_f6_resolve(u32 v)
> case SSB_CHIPCO_CLK_F6_7:
> return 7;
> }
> - return 0;
> + return 1;
> }
Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
Larry
>
> /* Calculate the speed the backplane would run at a given set of clockcontrol values */
next prev parent reply other threads:[~2023-09-05 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 23:23 Rand Deeb
2023-09-05 0:59 ` Larry Finger [this message]
2023-09-05 6:20 ` Michael Büsch
2023-09-07 6:00 ` Kalle Valo
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=96eb9ff2-a687-bbd5-9cb1-4b044f7deae3@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=deeb.rand@confident.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=m@bues.ch \
--cc=rand.sec96@gmail.com \
--cc=voskresenski.stanislav@confident.ru \
/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
all inboxes | Powered by JetHome®