From: walter harms <wharms@bfs.de>
To: Colin King <colin.king@canonical.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>, "Rex Zhu" <Rex.Zhu@amd.com>,
"Eric Huang" <JinHuiEric.Huang@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/powerplay: ensure loop does not wraparound on decrement
Date: Thu, 18 May 2017 09:15:51 +0200 [thread overview]
Message-ID: <591D4A27.7020402@bfs.de> (raw)
In-Reply-To: <20170517181346.11715-1-colin.king@canonical.com>
Am 17.05.2017 20:13, schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> The current for loop decrements i when it is zero and this causes
> a wrap-around back to ~0 because i is unsigned. In the unlikely event
> that mask is 0, the loop will run forever. Fix this so we can't loop
> forever.
>
> Detected by CoverityScan, CID#1435469 ("Unsigned compared against 0")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c b/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> index ad30f5d3a10d..d92c9b9b15be 100644
> --- a/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> +++ b/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> @@ -4199,7 +4199,7 @@ static int vega10_force_clock_level(struct pp_hwmgr *hwmgr,
> }
> data->smc_state_table.gfx_boot_level = i;
>
> - for (i = 31; i >= 0; i--) {
> + for (i = 32; --i; ) {
> if (mask & (1 << i))
> break;
> }
nitpicking:
we notices at several points that programmers are bad at counting backwards.
Is there a reason not to start with i=0 ?
re,
wh
WARNING: multiple messages have this Message-ID (diff)
From: walter harms <wharms@bfs.de>
To: Colin King <colin.king@canonical.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>, "Rex Zhu" <Rex.Zhu@amd.com>,
"Eric Huang" <JinHuiEric.Huang@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/powerplay: ensure loop does not wraparound on decrement
Date: Thu, 18 May 2017 07:15:51 +0000 [thread overview]
Message-ID: <591D4A27.7020402@bfs.de> (raw)
In-Reply-To: <20170517181346.11715-1-colin.king@canonical.com>
Am 17.05.2017 20:13, schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> The current for loop decrements i when it is zero and this causes
> a wrap-around back to ~0 because i is unsigned. In the unlikely event
> that mask is 0, the loop will run forever. Fix this so we can't loop
> forever.
>
> Detected by CoverityScan, CID#1435469 ("Unsigned compared against 0")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c b/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> index ad30f5d3a10d..d92c9b9b15be 100644
> --- a/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> +++ b/drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c
> @@ -4199,7 +4199,7 @@ static int vega10_force_clock_level(struct pp_hwmgr *hwmgr,
> }
> data->smc_state_table.gfx_boot_level = i;
>
> - for (i = 31; i >= 0; i--) {
> + for (i = 32; --i; ) {
> if (mask & (1 << i))
> break;
> }
nitpicking:
we notices at several points that programmers are bad at counting backwards.
Is there a reason not to start with i=0 ?
re,
wh
next prev parent reply other threads:[~2017-05-18 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 18:13 [PATCH] drm/amd/powerplay: ensure loop does not wraparound on decrement Colin King
2017-05-17 18:13 ` Colin King
2017-05-17 18:13 ` Colin King
2017-05-17 19:30 ` Dan Carpenter
2017-05-17 19:30 ` Dan Carpenter
2017-05-17 19:30 ` Dan Carpenter
2017-05-18 7:15 ` walter harms [this message]
2017-05-18 7:15 ` walter harms
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=591D4A27.7020402@bfs.de \
--to=wharms@bfs.de \
--cc=JinHuiEric.Huang@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=colin.king@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.