From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: Improve PPS SCC extension bit depth check
Date: Mon, 10 Jul 2023 03:19:44 +0200
Message-ID: <GV1P250MB0737EE39EA4944EFF776F56C8F30A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <23329244-d939-61cd-2cd1-47cecd343ef7@gmail.com>
James Almer:
> On 7/9/2023 9:19 PM, Andreas Rheinhardt wrote:
>> From the spec: "It is a requirement of bitstream conformance that
>> the value of luma_bit_depth_entry_minus8 shall be equal to
>> the value of bit_depth_luma_minus8"; similarly for chroma.
>>
>> Should fix Coverity ticket #1529226.
>>
>> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
>> ---
>> libavcodec/hevc_ps.c | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/libavcodec/hevc_ps.c b/libavcodec/hevc_ps.c
>> index 4c4c1e2c17..1db2d3a242 100644
>> --- a/libavcodec/hevc_ps.c
>> +++ b/libavcodec/hevc_ps.c
>> @@ -1581,11 +1581,13 @@ static int pps_scc_extension(GetBitContext
>> *gb, AVCodecContext *avctx,
>> }
>> pps->monochrome_palette_flag = get_bits1(gb);
>> pps->luma_bit_depth_entry = get_ue_golomb_31(gb) + 8;
>> - if (!pps->monochrome_palette_flag)
>> - pps->chroma_bit_depth_entry = get_ue_golomb_31(gb) + 8;
>> -
>> - if (pps->chroma_bit_depth_entry > 16 ||
>> pps->chroma_bit_depth_entry > 16)
>
> Is Coverity complaining about this duplicate check? If so, you should
> mention that fixing the Coverity issue is a side effect of the
> compliance check you're applying, rather than the actual objective of
> the change.
It's indeed about this duplicate check. It's how I found this issue.
>
> You could also replace one chroma_bit_depth_entry check with
> luma_bit_depth_entry in one commit, fixing the Coverity issue, then this
> compliance change in another.
>
I don't see why separating this in two commits would be beneficial
(except for my commit count, but I don't intentionally maximise that).
Patches are typically split into smaller parts to ease reviewing, but
this change is trivial either way (but a tiny bit less trivial when split).
>> + if (pps->luma_bit_depth_entry != sps->bit_depth)
>> return AVERROR_INVALIDDATA;
>> + if (!pps->monochrome_palette_flag) {
>> + pps->chroma_bit_depth_entry = get_ue_golomb_31(gb) + 8;
>> + if (pps->chroma_bit_depth_entry !=
>> sps->bit_depth_chroma)
>> + return AVERROR_INVALIDDATA;
>> + }
>> num_comps = pps->monochrome_palette_flag ? 1 : 3;
>> for (int comp = 0; comp < num_comps; comp++) {
>
> LGTM either way.
_______________________________________________
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".
prev parent reply other threads:[~2023-07-10 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 0:19 Andreas Rheinhardt
2023-07-10 0:56 ` James Almer
2023-07-10 1:19 ` Andreas Rheinhardt [this message]
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=GV1P250MB0737EE39EA4944EFF776F56C8F30A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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