From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/cbs_apv: don't return an error when reading empty buffers Date: Wed, 30 Apr 2025 18:18:42 -0300 Message-ID: <cdf328f0-2408-47d5-8eef-162e13624567@gmail.com> (raw) In-Reply-To: <af60e860-4ded-45d7-a50d-14f12dd422a2@jkqxz.net> [-- Attachment #1.1.1: Type: text/plain, Size: 1509 bytes --] On 4/30/2025 6:17 PM, Mark Thompson wrote: > On 29/04/2025 20:57, James Almer wrote: >> The output will be a fragment with zero units, which is a lot more user friendly >> than making them think something went wrong, as it already happens with cbs_av1. >> >> Signed-off-by: James Almer <jamrial@gmail.com> >> --- >> libavcodec/cbs_apv.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/libavcodec/cbs_apv.c b/libavcodec/cbs_apv.c >> index 2c4a1daaf0..66ea4cebab 100644 >> --- a/libavcodec/cbs_apv.c >> +++ b/libavcodec/cbs_apv.c >> @@ -175,7 +175,7 @@ static int cbs_apv_split_fragment(CodedBitstreamContext *ctx, >> >> if (frag->data_size < 4) { >> // Too small to be a valid fragment. >> - return AVERROR_INVALIDDATA; >> + return 0; >> } >> >> // Don't include parsing here in trace output. > > Seems fair for a zero-size buffer, but I don't like this for a three-byte fragment containing { 0xab, 0xcd, 0xef } - that feels like it should return an error. > > Maybe it would make more sense to have a separate check for zero. What do you think? Sure, will send an updated patch in a bit. > > Thanks, > > - Mark > > _______________________________________________ > 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". [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 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:[~2025-04-30 21:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-29 19:57 James Almer 2025-04-30 21:17 ` Mark Thompson 2025-04-30 21:18 ` James Almer [this message] 2025-04-30 21:22 ` [FFmpeg-devel] [PATCH v2] " James Almer 2025-04-30 22:13 ` Mark Thompson
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=cdf328f0-2408-47d5-8eef-162e13624567@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