From: Pierre-Anthony Lemieux <pal@sandflow.com> To: etemesicaleb@gmail.com Cc: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/jpeg2000dec: Explicitly cast quad_width and quad_height to size_t Date: Tue, 25 Apr 2023 13:13:56 -0700 Message-ID: <CAF_7JxDruR5E6usew433Vpa2_cbN6Wr+VnRNT8YikOrj5Yt25g@mail.gmail.com> (raw) In-Reply-To: <20230425182429.59726-1-etemesicaleb@gmail.com> On Tue, Apr 25, 2023 at 11:25 AM <etemesicaleb@gmail.com> wrote: > > From: caleb <etemesicaleb@gmail.com> > > Prevents un-necessary casts when calculating buf_size This is to address Coverity CID 1528149: """Suspicious implicit sign extension: "quad_height" with type "uint16_t const" (16 bits, unsigned) is promoted in "4 * quad_width * quad_height" to type "int" (32 bits, signed), then sign-extended to type "unsigned long" (64 bits, unsigned). If "4 * quad_width * quad_height" is greater than 0x7FFFFFFF, the upper bits of the result will all be 1.""" > --- > libavcodec/jpeg2000htdec.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/jpeg2000htdec.c b/libavcodec/jpeg2000htdec.c > index 51cd96e0f1..8907820806 100644 > --- a/libavcodec/jpeg2000htdec.c > +++ b/libavcodec/jpeg2000htdec.c > @@ -592,8 +592,8 @@ static int jpeg2000_decode_ht_cleanup_segment(const Jpeg2000DecoderContext *s, > const uint16_t is_border_x = width % 2; > const uint16_t is_border_y = height % 2; > > - const uint16_t quad_width = ff_jpeg2000_ceildivpow2(width, 1); > - const uint16_t quad_height = ff_jpeg2000_ceildivpow2(height, 1); > + const size_t quad_width = ff_jpeg2000_ceildivpow2(width, 1); > + const size_t quad_height = ff_jpeg2000_ceildivpow2(height, 1); Shouldn't quad_width and quad_height be kept as uint16_t, and instead be explicitly cast to (size_t) when computing buf_size? > > size_t buf_size = 4 * quad_width * quad_height; > > -- > 2.39.2 > _______________________________________________ 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:[~2023-04-25 20:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 18:24 etemesicaleb 2023-04-25 20:13 ` Pierre-Anthony Lemieux [this message] 2023-04-25 20:19 ` James Almer
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=CAF_7JxDruR5E6usew433Vpa2_cbN6Wr+VnRNT8YikOrj5Yt25g@mail.gmail.com \ --to=pal@sandflow.com \ --cc=etemesicaleb@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