From: Thilo Borgmann <thilo.borgmann@mail.de> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavc/dovi_rpu: Fix UB for possible left shift of negative values Date: Thu, 16 Jun 2022 13:19:03 +0200 Message-ID: <141157fa-3768-a187-81a7-52b89aa10787@mail.de> (raw) In-Reply-To: <DB6PR0101MB22146BF981BC98242F9180CD8FAC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> [-- Attachment #1: Type: text/plain, Size: 2427 bytes --] Am 16.06.22 um 12:40 schrieb Andreas Rheinhardt: > Thilo Borgmann: >> Am 16.06.22 um 12:13 schrieb Andreas Rheinhardt: >>> Thilo Borgmann: >>>> diff --git a/libavcodec/dovi_rpu.c b/libavcodec/dovi_rpu.c >>>> index a87562c8a3..833ce9e705 100644 >>>> --- a/libavcodec/dovi_rpu.c >>>> +++ b/libavcodec/dovi_rpu.c >>>> @@ -153,7 +153,7 @@ static inline uint64_t get_ue_coef(GetBitContext >>>> *gb, const AVDOVIRpuDataHeader >>>> case RPU_COEFF_FIXED: >>>> ipart = get_ue_golomb_long(gb); >>>> fpart.u32 = get_bits_long(gb, hdr->coef_log2_denom); >>>> - return (ipart << hdr->coef_log2_denom) + fpart.u32; >>>> + return ipart * (1 << hdr->coef_log2_denom) + fpart.u32; >>>> case RPU_COEFF_FLOAT: >>>> fpart.u32 = get_bits_long(gb, 32); >>>> @@ -172,7 +172,7 @@ static inline int64_t get_se_coef(GetBitContext >>>> *gb, const AVDOVIRpuDataHeader * >>>> case RPU_COEFF_FIXED: >>>> ipart = get_se_golomb_long(gb); >>>> fpart.u32 = get_bits_long(gb, hdr->coef_log2_denom); >>>> - return (ipart << hdr->coef_log2_denom) + fpart.u32; >>>> + return ipart * (1 << hdr->coef_log2_denom) + fpart.u32; >>>> case RPU_COEFF_FLOAT: >>>> fpart.u32 = get_bits_long(gb, 32); >>> >>> coef_log2_denom can be in the range 13..32. This means that 1 << >>> hdr->coef_log2_denom can be UB (namely if coef_log2_denom is 31 or 32 >>> for ordinary 32 bit ints); this time it is not UB that happens to work >>> as expected, because 1 << 32 will be 0 or 1 (depending upon the system) >>> and not 2^32. In case of get_ue_coef() this actually adds UB to >>> otherwise fine code. >> >> So 1LL it needs to be, not? Am I still missing something? >> > > This version should not add new UB. > I btw don't get why you are changing get_ue_coef() at all: It's fine > as-is; consistency should only trump when the choice is between several > equally good alternatives which is IMO not true here. (The reason that C > makes left shifts of negative values UB is because of non-two's > complement systems, so it is unfortunate for a project like FFmpeg that > requires two's complement that it has to workaround this restriction by > using a * (1 << b).) Just overthinking consistency, I guess. v4 changes get_se_coef() only. Thanks, Thilo [-- Attachment #2: v4-0001-lavc-dovi_rpu-Fix-UB-for-possible-left-shift-of-n.patch --] [-- Type: text/plain, Size: 975 bytes --] From 85429be17bf238642aeacf93e4d7c16d4c4b03a3 Mon Sep 17 00:00:00 2001 From: Michael Goulet <mgoulet@fb.com> Date: Thu, 16 Jun 2022 13:17:25 +0200 Subject: [PATCH v4] lavc/dovi_rpu: Fix UB for possible left shift of negative values It is undefined to left-shift a negative value. --- libavcodec/dovi_rpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/dovi_rpu.c b/libavcodec/dovi_rpu.c index a87562c8a3..dd38936552 100644 --- a/libavcodec/dovi_rpu.c +++ b/libavcodec/dovi_rpu.c @@ -172,7 +172,7 @@ static inline int64_t get_se_coef(GetBitContext *gb, const AVDOVIRpuDataHeader * case RPU_COEFF_FIXED: ipart = get_se_golomb_long(gb); fpart.u32 = get_bits_long(gb, hdr->coef_log2_denom); - return (ipart << hdr->coef_log2_denom) + fpart.u32; + return ipart * (1LL << hdr->coef_log2_denom) + fpart.u32; case RPU_COEFF_FLOAT: fpart.u32 = get_bits_long(gb, 32); -- 2.20.1 (Apple Git-117) [-- Attachment #3: 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:[~2022-06-16 11:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-16 8:59 Thilo Borgmann 2022-06-16 9:44 ` Andreas Rheinhardt 2022-06-16 10:04 ` Thilo Borgmann 2022-06-16 10:13 ` Andreas Rheinhardt 2022-06-16 10:22 ` Thilo Borgmann 2022-06-16 10:40 ` Andreas Rheinhardt 2022-06-16 11:19 ` Thilo Borgmann [this message] 2022-06-20 9:06 ` Thilo Borgmann 2022-06-21 16:24 ` Thilo Borgmann
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=141157fa-3768-a187-81a7-52b89aa10787@mail.de \ --to=thilo.borgmann@mail.de \ --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