Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/4] avcodec/ac3_parser: use a padded buffer in av_ac3_parse_header()
Date: Fri, 6 Jun 2025 02:32:54 +0200
Message-ID: <GV1P250MB073763CADD2B3F3D0B22E0498F6EA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <126036a0-6df1-4274-a4b3-2896126c6591@gmail.com>

James Almer:
> On 6/5/2025 9:29 PM, Andreas Rheinhardt wrote:
>> James Almer:
>>> The GetBitContext API requires the buffer to be padded, and the
>>> documentation for
>>> av_ac3_parse_header() does not specify it, so use a temporary local
>>> buffer.
>>>
>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>> ---
>>>   libavcodec/ac3_parser.c | 16 +++++++++++++---
>>>   1 file changed, 13 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/libavcodec/ac3_parser.c b/libavcodec/ac3_parser.c
>>> index 69989690dd..9065d700e2 100644
>>> --- a/libavcodec/ac3_parser.c
>>> +++ b/libavcodec/ac3_parser.c
>>> @@ -202,14 +202,24 @@ int av_ac3_parse_header(const uint8_t *buf,
>>> size_t size,
>>>   {
>>>       GetBitContext gb;
>>>       AC3HeaderInfo hdr;
>>> +    uint8_t *tmp = av_malloc(size + AV_INPUT_BUFFER_PADDING_SIZE);
>>>       int err;
>>>   -    err = init_get_bits8(&gb, buf, size);
>>> -    if (err < 0)
>>> +    if (!tmp)
>>> +        return AVERROR(ENOMEM);
>>> +
>>> +    memcpy(tmp, buf, size);
>>> +    memset(tmp + size, 0, AV_INPUT_BUFFER_PADDING_SIZE);
>>> +    err = init_get_bits8(&gb, tmp, size);
>>> +    if (err < 0) {
>>> +        av_free(tmp);
>>>           return AVERROR_INVALIDDATA;
>>> +    }
>>>       err = ff_ac3_parse_header(&gb, &hdr);
>>> -    if (err < 0)
>>> +    if (err < 0) {
>>> +        av_free(tmp);
>>>           return AVERROR_INVALIDDATA;
>>> +    }
>>>         *bitstream_id = hdr.bitstream_id;
>>>       *frame_size   = hdr.frame_size;
>>
>> There is no need for an allocation here; (E)AC-3 frames have a bounded
>> size and the number of bytes read by ff_ac3_parse_header() is even
>> smaller.
> 
> What's the max size? Is there a define for it?

Not yet.

> 
>> Anyway: The buffer leaks on success.
> 
> I'm aware, i said as much in a reply :p
> 

Should have read all your mails.

- 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".

  reply	other threads:[~2025-06-06  0:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  0:14 James Almer
2025-06-06  0:14 ` [FFmpeg-devel] [PATCH v2 2/4] avcodec/ac3_parser: handle more header bits in ff_ac3_parse_header() James Almer
2025-06-06  0:14 ` [FFmpeg-devel] [PATCH v2 3/4] avformat/movenc: fix writing reserved bits in EC3SpecificBox James Almer
2025-06-06  0:40   ` Baptiste Coudurier
2025-06-06  0:14 ` [FFmpeg-devel] [PATCH v2 4/4] avformat/movenc: handle EAC-3 extension bits for Atmos James Almer
2025-06-06  0:53   ` Baptiste Coudurier
2025-06-06  0:16 ` [FFmpeg-devel] [PATCH 1/4] avcodec/ac3_parser: use a padded buffer in av_ac3_parse_header() James Almer
2025-06-06  0:29 ` Andreas Rheinhardt
2025-06-06  0:31   ` James Almer
2025-06-06  0:32     ` Andreas Rheinhardt [this message]
2025-06-06  0:51       ` James Almer
2025-06-06  1:31         ` Andreas Rheinhardt
2025-06-06  1:42           ` [FFmpeg-devel] [PATCH v2 " James Almer
2025-06-08  0:19 ` [FFmpeg-devel] [PATCH " James Almer

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=GV1P250MB073763CADD2B3F3D0B22E0498F6EA@GV1P250MB0737.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