From: "Zhao Zhili" <quinkblack@foxmail.com> To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/4] avcodec/hevc_parse: check the size of hvcC is at least 23 Date: Wed, 14 Jun 2023 01:11:58 +0800 Message-ID: <tencent_C817DC6F8B89262BD084A6D167D32AB2D306@qq.com> (raw) In-Reply-To: <CAM=jba8L7w4aZKR59=GoguGYTzOwQZPnYsCuzALFe+QesTctvQ@mail.gmail.com> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lance Wang > Sent: 2023年6月13日 22:10 > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH 2/4] avcodec/hevc_parse: check the size of hvcC is at least 23 > > On Tue, Jun 13, 2023 at 3:37 PM Zhao Zhili <quinkblack@foxmail.com> wrote: > > > From: Zhao Zhili <zhilizhao@tencent.com> > > > > The code after the check skip 21 bytes and then read two bytes. > > > > Signed-off-by: Zhao Zhili <zhilizhao@tencent.com> > > --- > > libavcodec/hevc_parse.c | 4 +++- > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > diff --git a/libavcodec/hevc_parse.c b/libavcodec/hevc_parse.c > > index 1f3beed183..7bc28fd081 100644 > > --- a/libavcodec/hevc_parse.c > > +++ b/libavcodec/hevc_parse.c > > @@ -88,8 +88,10 @@ int ff_hevc_decode_extradata(const uint8_t *data, int > > size, HEVCParamSets *ps, > > > > /* data[0] == 1 is configurationVersion from 14496-15. > > * data[0] == 0 is for backward compatibility predates the standard. > > + * > > + * Minimum number of bytes of hvcC with 0 numOfArrays is 23. > > */ > > - if (size > 3 && ((data[0] == 1) || (data[0] == 0 && (data[1] || > > data[2] > 1)))) { > > + if (size >= 23 && ((data[0] == 1) || (data[0] == 0 && (data[1] || > > data[2] > 1)))) { > > > > I think it's better to move the size checking before 21 byte are skipped, > or it'll go to the else logic which > is different. It's not avcC if size is less than 23, go to the else branch is the intended behavior. > > /* It seems the extradata is encoded as hvcC format. */ > > int i, j, num_arrays, nal_len_size; > > > > -- > > 2.25.1 > > > > _______________________________________________ > > 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". > > > _______________________________________________ > 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". _______________________________________________ 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-06-13 17:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20230613073718.675388-1-quinkblack@foxmail.com> 2023-06-13 7:37 ` Zhao Zhili 2023-06-13 14:10 ` Lance Wang 2023-06-13 17:11 ` Zhao Zhili [this message] 2023-06-13 7:37 ` [FFmpeg-devel] [PATCH 3/4] avformat/asfdec_f: support bmp_tags_unofficial Zhao Zhili 2023-06-13 7:37 ` [FFmpeg-devel] [PATCH 4/4] avformat/asfdec_f: fix need_parsing flag for codec mpeg4 Zhao Zhili
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=tencent_C817DC6F8B89262BD084A6D167D32AB2D306@qq.com \ --to=quinkblack@foxmail.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