From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Increase IntraEdgeParams buffer size
Date: Mon, 29 Jan 2024 20:32:14 -0300
Message-ID: <3de88e6a-7aef-452d-bcb2-d8d2b48f1c77@gmail.com> (raw)
In-Reply-To: <20240129232104.4193951-1-post@frankplowman.com>
On 1/29/2024 8:22 PM, Frank Plowman wrote:
> The reference line buffers are used with indices in the range
> -MAX_TB_SIZE - 3 to refw + FFMAX(1, w/h) * ref_idx + 1, which is
> at most 5*MAX_TB_SIZE + 1.
>
> Fixes buffer overflows.
> http://fate.ffmpeg.org/report.cgi?slot=armv7-linux-gcc-9&time=20240124051736
> ---
> libavcodec/vvc/vvcdsp.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/libavcodec/vvc/vvcdsp.c b/libavcodec/vvc/vvcdsp.c
> index c82ea7be30..56e71d5163 100644
> --- a/libavcodec/vvc/vvcdsp.c
> +++ b/libavcodec/vvc/vvcdsp.c
> @@ -87,10 +87,10 @@ typedef struct IntraEdgeParams {
> uint8_t* left;
> int filter_flag;
>
> - uint16_t left_array[3 * MAX_TB_SIZE + 3];
> - uint16_t filtered_left_array[3 * MAX_TB_SIZE + 3];
> - uint16_t top_array[3 * MAX_TB_SIZE + 3];
> - uint16_t filtered_top_array[3 * MAX_TB_SIZE + 3];
> + uint16_t left_array[6 * MAX_TB_SIZE + 5];
> + uint16_t filtered_left_array[6 * MAX_TB_SIZE + 5];
> + uint16_t top_array[6 * MAX_TB_SIZE + 5];
> + uint16_t filtered_top_array[6 * MAX_TB_SIZE + 5];
> } IntraEdgeParams;
>
> #define PROF_BORDER_EXT 1
Applied, thanks.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2024-01-29 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 23:22 Frank Plowman
2024-01-29 23:32 ` James Almer [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=3de88e6a-7aef-452d-bcb2-d8d2b48f1c77@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git