From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Frank Plowman <post@frankplowman.com> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Reallocate pixel buffers if pixel shift changes Date: Tue, 4 Jun 2024 20:38:53 +0800 Message-ID: <CAFXK13eNz-dWp2=3zBSOpKxYQMbrOb2kuLe9MMeNT=qCrV1G2g@mail.gmail.com> (raw) In-Reply-To: <20240603130635.16140-1-post@frankplowman.com> On Mon, Jun 3, 2024 at 9:06 PM Frank Plowman <post@frankplowman.com> wrote: > Allocations in the following lines depend on the pixel shift, and so > these buffers must be reallocated if the pixel shift changes. Patch > fixes segmentation faults in fuzzed bitstreams. > > Signed-off-by: Frank Plowman <post@frankplowman.com> > --- > libavcodec/vvc/dec.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/vvc/dec.c b/libavcodec/vvc/dec.c > index e53ad4e607..f5603306f3 100644 > --- a/libavcodec/vvc/dec.c > +++ b/libavcodec/vvc/dec.c > @@ -214,7 +214,8 @@ static void pixel_buffer_nz_tl_init(TabList *l, > VVCFrameContext *fc) > const int c_end = chroma_idc ? VVC_MAX_SAMPLE_ARRAYS : 1; > const int changed = fc->tab.sz.chroma_format_idc != chroma_idc || > fc->tab.sz.width != width || fc->tab.sz.height != height || > - fc->tab.sz.ctu_width != ctu_width || fc->tab.sz.ctu_height != > ctu_height; > + fc->tab.sz.ctu_width != ctu_width || fc->tab.sz.ctu_height != > ctu_height || > + fc->tab.sz.pixel_shift != ps; > > Applied. Thank you, Frank. > tl_init(l, 0, changed); > > -- > 2.45.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".
prev parent reply other threads:[~2024-06-04 12:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-03 13:06 Frank Plowman 2024-06-04 12:38 ` Nuo Mi [this message]
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='CAFXK13eNz-dWp2=3zBSOpKxYQMbrOb2kuLe9MMeNT=qCrV1G2g@mail.gmail.com' \ --to=nuomi2021@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=post@frankplowman.com \ /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