From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: "Harry Wentland" <harry.wentland@amd.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
"David Airlie" <airlied@linux.ie>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/display/dc/dce: Fix multiple potential integer overflows
Date: Wed, 4 Jul 2018 12:54:22 -0500 [thread overview]
Message-ID: <ab3d5e10-e25b-46a1-d3ab-da3619d8c5b4@embeddedor.com> (raw)
In-Reply-To: <421747e5-e6e0-6680-e3b7-a3a2a5b7b307@amd.com>
On 07/04/2018 12:51 PM, Harry Wentland wrote:
[..]
>>>
>>> @@ -145,8 +145,8 @@ static bool calculate_fb_and_fractional_fb_divider(
>>> * of fractional feedback decimal point and the fractional FB Divider precision
>>> * is 2 then the equation becomes (ullfeedbackDivider + 5*100) / (10*100))*/
>>>
>>> - feedback_divider += (uint64_t)
>>> - (5 * calc_pll_cs->fract_fb_divider_precision_factor);
>>> + feedback_divider += 5UL *
>>> + calc_pll_cs->fract_fb_divider_precision_factor;
>>
>> This should be 5ULL, as the commit log says, otherwise it's still only
>> 32 bits on 32-bit platforms.
>>
>
> Agreed.
>
> Otherwise this looks good.
>
> With that fixed this patch is
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
Hi Harry,
I already sent v2: https://patchwork.kernel.org/patch/10506897/
Thanks
--
Gustavo
next prev parent reply other threads:[~2018-07-04 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 1:13 Gustavo A. R. Silva
2018-07-04 7:38 ` Michel Dänzer
2018-07-04 12:51 ` Gustavo A. R. Silva
2018-07-04 17:51 ` Harry Wentland
2018-07-04 17:54 ` Gustavo A. R. Silva [this message]
2018-07-04 18:05 ` Harry Wentland
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=ab3d5e10-e25b-46a1-d3ab-da3619d8c5b4@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=David1.Zhou@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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
Powered by JetHome