From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/cuviddec: fix AV1 decoding error Date: Fri, 24 Jun 2022 09:06:31 -0300 Message-ID: <759c7662-ea42-0e31-d107-bbff05ff9820@gmail.com> (raw) In-Reply-To: <tencent_6168FE7DD2ACDE3899C251B6B46B7E00850A@qq.com> On 6/24/2022 1:04 AM, Zhao Zhili wrote: > From: Zhao Zhili <zhilizhao@tencent.com> > > cuvidParseVideoData only supports pure OBUs, it report unknown > error with AV1CodecConfigurationRecord. Check whether extradata > is AV1CodecConfigurationRecord and skip the first 4 bytes to fix > the issue. > > The bug is revealed in ffmpeg cmd since 45e3b6a68 and ffd1316e. > --- > libavcodec/cuviddec.c | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/libavcodec/cuviddec.c b/libavcodec/cuviddec.c > index cb3cda7e24..fc9c0515fe 100644 > --- a/libavcodec/cuviddec.c > +++ b/libavcodec/cuviddec.c > @@ -953,6 +953,16 @@ static av_cold int cuvid_decode_init(AVCodecContext *avctx) > extradata_size = avctx->extradata_size; > } > > + // Check first bit to determine whether it's AV1CodecConfigurationRecord. > + // Skip first 4 bytes of AV1CodecConfigurationRecord to keep configOBUs > + // only, otherwise cuvidParseVideoData report unknown error. > + if (avctx->codec->id == AV_CODEC_ID_AV1 && > + extradata_size > 4 && > + extradata && extradata[0] & 0x80) { IMO the check for extradata here is unnecessary as the memcpy dereferencing it below will crash anyway if it were NULL. If anything, a check like (avctx->extradata_size || !avctx->extradata) should be added to avcodec_open2() if there isn't one already to ensure the user set up valid extradata when opening a decoder. > + extradata += 4; > + extradata_size -= 4; > + } > + > ctx->cuparse_ext = av_mallocz(sizeof(*ctx->cuparse_ext) > + FFMAX(extradata_size - (int)sizeof(ctx->cuparse_ext->raw_seqhdr_data), 0)); > if (!ctx->cuparse_ext) { LGTM either way. _______________________________________________ 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:[~2022-06-24 12:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-24 4:04 Zhao Zhili 2022-06-24 12:06 ` James Almer [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-06-23 9:10 Zhao Zhili 2022-06-23 14:14 ` Timo Rothenpieler 2022-06-24 2:52 ` "zhilizhao(赵志立)" 2022-06-24 4:09 ` "zhilizhao(赵志立)"
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=759c7662-ea42-0e31-d107-bbff05ff9820@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