From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 3/7] avformat/matroskadec: export Dynamic HDR10+ packet side data
Date: Wed, 29 Mar 2023 22:51:09 -0300
Message-ID: <6c6b331b-9caf-1b5c-559c-cf4edc78281e@gmail.com> (raw)
In-Reply-To: <GV1P250MB073736A3EFDEEE1A84DE7B4F8F8E9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On 3/29/2023 9:43 PM, Andreas Rheinhardt wrote:
>> @@ -3615,12 +3635,58 @@ static int matroska_parse_webvtt(MatroskaDemuxContext *matroska,
>> }
>>
>> static int matroska_parse_block_additional(MatroskaDemuxContext *matroska,
>> - AVPacket *pkt,
>> + MatroskaTrack *track, AVPacket *pkt,
>> const uint8_t *data, int size, uint64_t id)
>> {
>> - uint8_t *side_data = av_packet_new_side_data(pkt,
>> - AV_PKT_DATA_MATROSKA_BLOCKADDITIONAL,
>> - size + 8);
>> + uint8_t *side_data;
>> + int res;
>> +
>> + switch (id) {
>> + case 4: {
>> + GetByteContext bc;
>> + int country_code, provider_code;
>> + int provider_oriented_code, application_identifier;
>> + size_t hdrplus_size;
>> + AVDynamicHDRPlus *hdrplus;
>> +
>> + if (!track->blockaddid_itu_t_t35)
>> + break; //ignore
>> +
>> + bytestream2_init(&bc, data, size);
>> +
>> + /* ITU-T T.35 metadata */
>> + country_code = bytestream2_get_byte(&bc);
>> + provider_code = bytestream2_get_be16(&bc);
> This will add implicit overread checks; but you should check size
> explicitly instead.
> (The current behaviour of the bytestream2 API is to return 0 upon
> overreads; yet one should not rely on this and it could e.g. be changed
> so that bytestream2_get_byte returns 0xB5 and bytestream2_get_be16 0x3C
> upon overread.)
The only reason I'm using bytestream2 here was to not do a size check,
as Anton suggested.
Added one in any case, as well as using the u variants of
bytestream2_get_* since it will not overread now.
_______________________________________________
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:[~2023-03-30 1:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 15:52 [FFmpeg-devel] [PATCH v2 1/7] avformat/matroskadec: support parsing more than one BlockMore element James Almer
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v2 2/7] avformat/matroskadec: set the default value for BlockAddIDType James Almer
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v2 3/7] avformat/matroskadec: export Dynamic HDR10+ packet side data James Almer
2023-03-30 0:43 ` Andreas Rheinhardt
2023-03-30 1:51 ` James Almer [this message]
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v2 4/7] avformat/matroska: add a few more Block Addition ID Type enum values James Almer
2023-03-30 0:43 ` Andreas Rheinhardt
2023-03-30 0:48 ` James Almer
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v3 5/7] avformat/matroskaenc: write a MaxBlockAdditionID element James Almer
2023-03-25 11:39 ` Michael Niedermayer
2023-03-25 11:40 ` James Almer
2023-03-30 0:44 ` Andreas Rheinhardt
2023-03-30 1:28 ` James Almer
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v3 6/7] avformat/matroskaenc: support writing Dynamic HDR10+ packet side data James Almer
2023-03-28 15:33 ` [FFmpeg-devel] [PATCH v4 " James Almer
2023-03-30 0:44 ` [FFmpeg-devel] [PATCH v3 " Andreas Rheinhardt
2023-03-30 1:41 ` James Almer
2023-03-24 15:52 ` [FFmpeg-devel] [PATCH v3 7/7] fate/matroska: add HDR10+ muxing tests James Almer
2023-03-30 0:43 ` [FFmpeg-devel] [PATCH v2 1/7] avformat/matroskadec: support parsing more than one BlockMore element Andreas Rheinhardt
2023-03-30 0:57 ` 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=6c6b331b-9caf-1b5c-559c-cf4edc78281e@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