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 18:13:44 -0300
Message-ID: <de78c01e-61e8-4e54-9cc6-f9b77d84525a@gmail.com> (raw)
In-Reply-To: <6567dce9-8a50-44d0-86eb-c78df3c1f5bc@frankplowman.com>
On 1/29/2024 5:19 PM, Frank Plowman wrote:
> On 29/01/2024 19:04, James Almer wrote:
>
>>
>> Well, turns out the current code is fine and my suggested change above
>> is wrong. Fun how that goes.
>>
>> Can you test the following instead?
>>
>>> diff --git a/libavcodec/cbs_h266_syntax_template.c
>>> b/libavcodec/cbs_h266_syntax_template.c
>>> index 549d021211..30b4ae3bc0 100644
>>> --- a/libavcodec/cbs_h266_syntax_template.c
>>> +++ b/libavcodec/cbs_h266_syntax_template.c
>>> @@ -764,7 +764,7 @@ static int FUNC(vps) (CodedBitstreamContext *ctx,
>>> RWContext *rw,
>>> infer(vps_each_layer_is_an_ols_flag, 0);
>>> if (!current->vps_each_layer_is_an_ols_flag) {
>>> if (!current->vps_all_independent_layers_flag)
>>> - ub(2, vps_ols_mode_idc);
>>> + u(2, vps_ols_mode_idc, 0, 2);
>>> else
>>> infer(vps_ols_mode_idc, 2);
>>> if (current->vps_ols_mode_idc == 2) {
> The spec reads "Decoders conforming to this version of this
> Specification shall *ignore* the OLSs with
> vps_ols_mode_idc equal to 3." This change throws an error for these
> OLSs, which I don't think is correct.
> There is already some logic just below this to warn the user if
> vps_ols_mode_idc is 3.
>>> @@ -902,11 +902,10 @@ static int FUNC(vps) (CodedBitstreamContext
>>> *ctx, RWContext *rw,
>>> current->vps_ols_mode_idc == 1) {
>>> num_layers_in_ols = i + 1;
>>> } else if (current->vps_ols_mode_idc == 2) {
>>> - for (k = 0, j = 0; k <=
>>> current->vps_max_layers_minus1; k++) {
>>> + for (k = 0, j = 0; k <=
>>> current->vps_max_layers_minus1; k++)
>>> if (layer_included_in_ols_flag[i][k])
>>> j++;
>>> - num_layers_in_ols = j;
>>> - }
>>> + num_layers_in_ols = j;
>>> }
>>> if (num_layers_in_ols > 1) {
>>> num_multi_layer_olss++;
>
> This looks good to me, the old behaviour was wrong. I don't think this
> is what was causing this
> particular crash however.
Will apply this part then.
>
> 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, so I'd expect it to also be at least 1 for
vps_each_layer_is_an_ols_flag == false.
> if (current->vps_each_layer_is_an_ols_flag)
> vps_num_dpb_params = 0;
> else
> @@ -991,7 +992,7 @@ static int FUNC(vps) (CodedBitstreamContext *ctx,
> RWContext *rw,
> else
> infer(vps_sublayer_cpb_params_present_flag, 0);
> ue(vps_num_ols_timing_hrd_params_minus1, 0,
> - num_multi_layer_olss - 1);
> + num_multi_layer_olss > 0 ? num_multi_layer_olss - 1 : 0);
> for (i = 0; i <=
> current->vps_num_ols_timing_hrd_params_minus1; i++) {
> uint8_t first_sublayer;
> if (!current->vps_default_ptl_dpb_hrd_max_tid_flag)
>
> _______________________________________________
> 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".
next prev parent reply other threads:[~2024-01-29 21:13 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 [this message]
2024-01-29 22:28 ` Frank Plowman
2024-01-29 23:40 ` James Almer
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=de78c01e-61e8-4e54-9cc6-f9b77d84525a@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