From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: wenyang.linux@foxmail.com,
Alex Deucher <alexander.deucher@amd.com>,
Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/display: fix array-bounds errors in dc_stream_remove_writeback()
Date: Wed, 4 Jan 2023 17:22:46 -0500 [thread overview]
Message-ID: <f848623a-a1de-23f1-3334-5cf4ea0f4d89@amd.com> (raw)
In-Reply-To: <tencent_13506618BF90E7B2AA796A9920DC49BEF407@qq.com>
On 12/25/22 10:10, wenyang.linux@foxmail.com wrote:
> From: Wen Yang <wenyang.linux@foxmail.com>
>
> The following errors occurred when using gcc 7.5.0-3ubuntu1~18.04:
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.c: In function ‘dc_stream_remove_writeback’:
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.c:543:55: warning: array subscript is above array bounds [-Warray-bounds]
> stream->writeback_info[j] = stream->writeback_info[i];
> ~~~~~~~~~~~~~~~~~~~~~~^~~
> Add a check to make sure that num_wb_info won't overflowing the writeback_info buffer.
>
> Fixes: 6fbefb84a98e ("drm/amd/display: Add DC core changes for DCN2")
>
> Signed-off-by: Wen Yang <wenyang.linux@foxmail.com>
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Hamza Mahfooz <hamza.mahfooz@amd.com>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Leo Li <sunpeng.li@amd.com>
> Cc: amd-gfx@lists.freedesktop.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
Applied, thanks!
> ---
> drivers/gpu/drm/amd/display/dc/core/dc_stream.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> index 20e534f73513..9825c30f2ca0 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> @@ -481,6 +481,7 @@ bool dc_stream_add_writeback(struct dc *dc,
> }
>
> if (!isDrc) {
> + ASSERT(stream->num_wb_info + 1 <= MAX_DWB_PIPES);
> stream->writeback_info[stream->num_wb_info++] = *wb_info;
> }
>
> @@ -526,6 +527,11 @@ bool dc_stream_remove_writeback(struct dc *dc,
> return false;
> }
>
> + if (stream->num_wb_info > MAX_DWB_PIPES) {
> + dm_error("DC: num_wb_info is invalid!\n");
> + return false;
> + }
> +
> // stream->writeback_info[dwb_pipe_inst].wb_enabled = false;
> for (i = 0; i < stream->num_wb_info; i++) {
> /*dynamic update*/
> @@ -540,7 +546,8 @@ bool dc_stream_remove_writeback(struct dc *dc,
> if (stream->writeback_info[i].wb_enabled) {
> if (j < i)
> /* trim the array */
> - stream->writeback_info[j] = stream->writeback_info[i];
> + memcpy(&stream->writeback_info[j], &stream->writeback_info[i],
> + sizeof(struct dc_writeback_info));
> j++;
> }
> }
--
Hamza
prev parent reply other threads:[~2023-01-04 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 15:10 wenyang.linux
2023-01-04 22:22 ` Hamza Mahfooz [this message]
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=f848623a-a1de-23f1-3334-5cf4ea0f4d89@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sunpeng.li@amd.com \
--cc=wenyang.linux@foxmail.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
all inboxes | Powered by JetHome®