From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Check fc->ref contains valid reference Date: Tue, 13 Feb 2024 11:03:11 +0800 Message-ID: <CAFXK13dmwBvRuEjO+apH1jFggSekNEKzs91tU8djE0OrXPaF=Q@mail.gmail.com> (raw) In-Reply-To: <632a0536-a339-4649-b8b2-9acdefa2cb01@frankplowman.com> On Fri, Feb 9, 2024 at 6:46 AM Frank Plowman <post@frankplowman.com> wrote: > > > On 08/02/2024 21:50, Lynne wrote: > > Feb 8, 2024, 22:16 by post@frankplowman.com: > > > >> From: Frank Plowman <post@frankplowman.com> > >> > >> Depending on where exactly decode_nal_unit failed, it is possible that > >> fc->ref holds a VVCFrame which has had ff_vvc_unref_frame called on it > >> and not yet had ref_frame called on it. In this case, fc->ref most of > >> the fields of fc->ref are NULL and attempting to call > >> ff_vvc_report_frame_finished on it will result in a null dereference. > >> > >> Patch fixes the error described above by checking fc->ref has not only > >> been allocated, but also references a valid AVFrame before attempting to > >> call ff_vvc_report_frame_finished on it. > >> > >> Signed-off-by: Frank Plowman <post@frankplowman.com> > >> --- > >> libavcodec/vvc/vvcdec.c | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/libavcodec/vvc/vvcdec.c b/libavcodec/vvc/vvcdec.c > >> index 8163b5ecb6..246ee79299 100644 > >> --- a/libavcodec/vvc/vvcdec.c > >> +++ b/libavcodec/vvc/vvcdec.c > >> @@ -820,7 +820,7 @@ static int decode_nal_units(VVCContext *s, > VVCFrameContext *fc, AVPacket *avpkt) > >> return 0; > >> > >> fail: > >> - if (fc->ref) > >> + if (fc->ref && fc->ref->frame->buf[0]) > >> ff_vvc_report_frame_finished(fc->ref); > >> return ret; > >> } > >> > > > > In general, for other codecs, if a reference does not exist, > > we simply allocate it and pretend it existed and was correctly decoded. > > This has better resilience against corrupt bitstreams or just bad muxing, > > and yields an (maybe corrupt) output, which is better than nothing. > > > > Is this not possible for VVC? > > I think the naming is confusing here. fc->ref is a pointer to the > VVCFrame currently being decoded. > HI Lynee, the name is from hevc. I do not like it either, but so many functions copied from hevc will use it. ... Hi Frank, Please try https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=10775 thank you > > -- > Frank > _______________________________________________ > 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:[~2024-02-13 3:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-08 21:16 post 2024-02-08 21:50 ` Lynne 2024-02-08 22:46 ` Frank Plowman 2024-02-13 3:03 ` Nuo Mi [this message] 2024-02-16 11:15 ` Anton Khirnov
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='CAFXK13dmwBvRuEjO+apH1jFggSekNEKzs91tU8djE0OrXPaF=Q@mail.gmail.com' \ --to=nuomi2021@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