From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] mpeg12enc: fix wrong size when copying A53_CC side-data into output
Date: Fri, 16 May 2025 03:15:09 +0200
Message-ID: <AS8P250MB074413F7B9D4C124F6973C808F93A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250516010538.886453-1-programmerjake@gmail.com>
Jacob Lifshay:
> Fixes: https://trac.ffmpeg.org/ticket/11591
>
> Signed-off-by: Jacob Lifshay <programmerjake@gmail.com>
> ---
> libavcodec/mpeg12enc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/mpeg12enc.c b/libavcodec/mpeg12enc.c
> index 8364368fde..e48437eb8a 100644
> --- a/libavcodec/mpeg12enc.c
> +++ b/libavcodec/mpeg12enc.c
> @@ -472,7 +472,7 @@ static int mpeg1_encode_picture_header(MPVMainEncContext *const m)
> (side_data->size / 3 & A53_MAX_CC_COUNT) | 0x40); // flags, cc_count
> put_bits(&s->pb, 8, 0xff); // em_data
>
> - ff_copy_bits(&s->pb, side_data->data, side_data->size);
> + ff_copy_bits(&s->pb, side_data->data, side_data->size * 8);
>
> put_bits(&s->pb, 8, 0xff); // marker_bits
> } else {
Thanks for this patch (and for the bug report; and sorry for causing you
trouble). Your patch was also my first attempt to fix this, but
unfortunately ff_copy_bits() may overread, yet the side data buffer need
not be padded, so my patch simply reverts the ff_copy_bits().
- Andreas
_______________________________________________
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".
next prev parent reply other threads:[~2025-05-16 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 1:05 Jacob Lifshay
2025-05-16 1:15 ` Andreas Rheinhardt [this message]
2025-05-16 1:29 ` Jacob Lifshay
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=AS8P250MB074413F7B9D4C124F6973C808F93A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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