From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avformat/avidec: Fix integer overflow iff ULONG_MAX < INT64_MAX Date: Tue, 12 Mar 2024 20:51:56 -0300 Message-ID: <b7e23f0c-3ba9-4e84-88fd-329c09a121e5@gmail.com> (raw) In-Reply-To: <AS8P250MB0744155F6451E58135C570E18F2B2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On 3/12/2024 8:01 PM, Andreas Rheinhardt wrote: > James Almer: >> On 3/12/2024 7:57 PM, Andreas Rheinhardt wrote: >>> Affects many FATE-tests, see >>> http://fate.ffmpeg.org/report.cgi?time=20240312011016&slot=ppc-linux-gcc-13.2-ubsan-altivec-qemu >>> >>> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> >>> --- >>> libavformat/avidec.c | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/libavformat/avidec.c b/libavformat/avidec.c >>> index f3183b2698..b7cbf148af 100644 >>> --- a/libavformat/avidec.c >>> +++ b/libavformat/avidec.c >>> @@ -1696,7 +1696,7 @@ static int >>> check_stream_max_drift(AVFormatContext *s) >>> int *idx = av_calloc(s->nb_streams, sizeof(*idx)); >>> if (!idx) >>> return AVERROR(ENOMEM); >>> - for (min_pos = pos = 0; min_pos != INT64_MAX; pos = min_pos + 1LU) { >>> + for (min_pos = pos = 0; min_pos != INT64_MAX; pos = min_pos + >>> (uint64_t)1) { >> >> nit: 1ULL >> > > The other variables are int64_t, not long long int, so using uint64_t is > appropriate. In practice it's not only the same, but also cleaner looking and done all across the codebase. But if you really want it to be uint64_t, then maybe use UINT64_C(1) instead (which, fwiw, will be expanded to 1ULL or even 1UL depending on target). > > - Andreas _______________________________________________ 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-03-12 23:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-12 22:57 Andreas Rheinhardt 2024-03-12 22:58 ` James Almer 2024-03-12 23:01 ` Andreas Rheinhardt 2024-03-12 23:51 ` James Almer [this message] 2024-03-14 19:52 ` Sean McGovern
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=b7e23f0c-3ba9-4e84-88fd-329c09a121e5@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