From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/4] avcodec/rtv1: Check if the minimal size is available in decode_rtv1() Date: Fri, 22 Sep 2023 23:52:15 +0200 Message-ID: <20230922215215.GA3543730@pb2> (raw) In-Reply-To: <CAPYw7P7Tm5EDvhpsZ-dv_1i1sKagxzAecVNvPYjerTWrdb4EaA@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1506 bytes --] On Fri, Sep 22, 2023 at 11:30:37PM +0200, Paul B Mahol wrote: > On 9/22/23, Michael Niedermayer <michael@niedermayer.cc> wrote: > > On Fri, Sep 22, 2023 at 09:32:47PM +0200, Paul B Mahol wrote: > >> On 9/22/23, Michael Niedermayer <michael@niedermayer.cc> wrote: > >> > On Thu, Jul 27, 2023 at 01:59:13AM +0200, Michael Niedermayer wrote: > >> >> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > >> >> --- > >> >> libavcodec/rtv1.c | 6 +++++- > >> >> 1 file changed, 5 insertions(+), 1 deletion(-) > >> > > >> > will apply 1-3 of this patchset > >> > >> Are you sure this does not break decoding? > > > > Well, its a loop over 4x4 blocks, a 16bit "skip" run so the minimum > > check looks correct. > > There are 2 end of bitstream checks for early exit but they look like > > error handling not some normal exit as they leave the frame uninitialized > > > > FFmpeg default initialization code for AVFrame's buffers does it > twice, so they are always zeroed or previous values of previous > buffers in pool. its rare that correct frame decoding depends on internal AVFrame buffer ordering > > > Do you have some files so i can double check this is not breaking anything > > Search trac tickets. thanks, found a zip with 2 video files ill check it [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB "I am not trying to be anyone's saviour, I'm trying to think about the future and not be sad" - Elon Musk [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-09-22 21:52 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-26 23:59 Michael Niedermayer 2023-07-26 23:59 ` [FFmpeg-devel] [PATCH 2/4] tools/target_dec_fuzzer: Adjust threshold for rtv1 Michael Niedermayer 2023-07-26 23:59 ` [FFmpeg-devel] [PATCH 3/4] avcodec/vvc_parser: Avoid undefined overflow in POC computation Michael Niedermayer 2023-07-26 23:59 ` [FFmpeg-devel] [PATCH 4/4] avcodec/evc_ps: Check num_ref_pic_list_in_sps Michael Niedermayer 2023-07-27 0:19 ` James Almer 2023-07-27 17:38 ` Michael Niedermayer 2023-09-22 19:22 ` [FFmpeg-devel] [PATCH 1/4] avcodec/rtv1: Check if the minimal size is available in decode_rtv1() Michael Niedermayer 2023-09-22 19:32 ` Paul B Mahol 2023-09-22 21:26 ` Michael Niedermayer 2023-09-22 21:30 ` Paul B Mahol 2023-09-22 21:52 ` Michael Niedermayer [this message] 2023-09-22 22:01 ` Paul B Mahol 2023-09-22 22:33 ` Michael Niedermayer 2023-09-22 22:46 ` Paul B Mahol
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=20230922215215.GA3543730@pb2 \ --to=michael@niedermayer.cc \ --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