From: Kieran Kunhya <kierank@obe.tv> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/h2645_parse: Avoid EAGAIN Date: Sun, 1 Oct 2023 20:24:57 +0200 Message-ID: <CAK+ULv6W-JEo_q5Y_oo2vVrqHT8-HNzTvN7h3VidcAN_oXgZWw@mail.gmail.com> (raw) In-Reply-To: <20231001180106.27631-1-michael@niedermayer.cc> Sent from my mobile device On Sun, 1 Oct 2023, 20:01 Michael Niedermayer, <michael@niedermayer.cc> wrote: > EAGAIN causes an assertion failure when it is returned from the decoder > > Fixes: Assertion consumed != (-(11)) failed at libavcodec/decode.c:462 > Fixes: assertion_IOT_instruction_decode_c_462/poc > > Found-by: Hardik Shah of Vehere (Dawn Treaders team) > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > libavcodec/h2645_parse.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/h2645_parse.h b/libavcodec/h2645_parse.h > index 787ce971ee4..128dea09efb 100644 > --- a/libavcodec/h2645_parse.h > +++ b/libavcodec/h2645_parse.h > @@ -123,7 +123,7 @@ static inline int get_nalsize(int nal_length_size, > const uint8_t *buf, > > if (*buf_index >= buf_size - nal_length_size) { > // the end of the buffer is reached, refill it > - return AVERROR(EAGAIN); > + return AVERROR_INVALIDDATA; > } > > for (i = 0; i < nal_length_size; i++) > -- > 2.17.1 > But these are not the same for an API user? Kieran > _______________________________________________ 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-10-01 18:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-01 18:01 Michael Niedermayer 2023-10-01 18:24 ` Kieran Kunhya [this message] 2023-10-01 18:35 ` Michael Niedermayer 2023-10-01 19:40 ` James Almer 2023-10-15 23:16 ` Michael Niedermayer
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=CAK+ULv6W-JEo_q5Y_oo2vVrqHT8-HNzTvN7h3VidcAN_oXgZWw@mail.gmail.com \ --to=kierank@obe.tv \ --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