From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/3] avcodec/cbs_h266_syntax_template: sanity check num_multi_layer_olss Date: Mon, 29 Jan 2024 20:40:16 -0300 Message-ID: <71450bd9-f4e6-49bc-bd32-3e6e8e87a4c9@gmail.com> (raw) In-Reply-To: <c7c97996-6f5d-4c93-98ad-d6bc0ab6e36f@frankplowman.com> On 1/29/2024 7:28 PM, Frank Plowman wrote: > > On 29/01/2024 21:13, James Almer wrote: >> On 1/29/2024 5:19 PM, Frank Plowman wrote: >>> Below is a patch which addresses the issue, an integer overflow when >>> calculating the bounds for >>> vps_num_ols_timing_hrd_params_minus1. There's also a similar fix for >>> vps_num_dpb_params_minus1. >>> >>> diff --git a/libavcodec/cbs_h266_syntax_template.c >>> b/libavcodec/cbs_h266_syntax_template.c >>> index 549d021211..49bf2e45ac 100644 >>> --- a/libavcodec/cbs_h266_syntax_template.c >>> +++ b/libavcodec/cbs_h266_syntax_template.c >>> @@ -946,7 +946,8 @@ static int FUNC(vps) (CodedBitstreamContext *ctx, >>> RWContext *rw, >>> >>> if (!current->vps_each_layer_is_an_ols_flag) { >>> uint16_t vps_num_dpb_params; >>> - ue(vps_num_dpb_params_minus1, 0, num_multi_layer_olss - 1); >>> + ue(vps_num_dpb_params_minus1, 0, >>> + num_multi_layer_olss > 0 ? num_multi_layer_olss - 1 : 0); >> >> FFMAX(0, num_multi_layer_olss - 1); looks better. >> >> If the spec explicitly states num_multi_layer_olss - 1 should be used >> here, wouldn't that mean that it doesn't expect num_multi_layer_olss >> to be 0 at this point for vps_ols_mode_idc >= 0 && vps_ols_mode_idc < 3? >> When vps_each_layer_is_an_ols_flag is true, num_multi_layer_olss is >> inferred as 1 > > num_multi_layer_olss is 0 if vps_each_layer_is_an_ols_flag is true, it > is num_layers_in_ols which must be 1. You're right, i read it wrong. These names are all too similar :p > >> so I'd expect it to also be at least 1 for >> vps_each_layer_is_an_ols_flag == false. > > Yes I think you're right. The spec isn't especially clear, but the > description of the vps_each_layer_is_an_ols_flag leads me to believe we > are safe to assert that. Patch which does so below. > > diff --git a/libavcodec/cbs_h266_syntax_template.c > b/libavcodec/cbs_h266_syntax_template.c > index 549d021211..5ae3fb9f08 100644 > --- a/libavcodec/cbs_h266_syntax_template.c > +++ b/libavcodec/cbs_h266_syntax_template.c > @@ -912,6 +912,8 @@ static int FUNC(vps) (CodedBitstreamContext *ctx, > RWContext *rw, > num_multi_layer_olss++; > } > } > + if (!current->vps_each_layer_is_an_ols_flag && > num_multi_layer_olss == 0) > + return AVERROR_INVALIDDATA; > } LGTM, can you send a patch for it? _______________________________________________ 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-01-29 23:40 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-26 21:46 [FFmpeg-devel] [PATCH 1/3] avcodec/vvc/vvcdec: Do not submit frames without VVCFrameThread Michael Niedermayer 2024-01-26 21:46 ` [FFmpeg-devel] [PATCH 2/3] avcodec/cbs_h266_syntax_template: sanity check num_multi_layer_olss Michael Niedermayer 2024-01-27 12:25 ` James Almer 2024-01-27 23:56 ` Michael Niedermayer 2024-01-28 0:02 ` James Almer 2024-01-28 0:05 ` Michael Niedermayer 2024-01-29 19:04 ` James Almer 2024-01-29 20:19 ` Frank Plowman 2024-01-29 21:13 ` James Almer 2024-01-29 22:28 ` Frank Plowman 2024-01-29 23:40 ` James Almer [this message] 2024-01-26 21:46 ` [FFmpeg-devel] [PATCH 3/3] avcodec/vvc/vvc_ps: check aps_adaptation_parameter_set_id Michael Niedermayer 2024-01-26 22:17 ` James Almer 2024-04-01 17:06 ` [FFmpeg-devel] [PATCH 1/3] avcodec/vvc/vvcdec: Do not submit frames without VVCFrameThread Michael Niedermayer 2024-04-02 2:50 ` Nuo Mi
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=71450bd9-f4e6-49bc-bd32-3e6e8e87a4c9@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