From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/6] avformat/avidec: support huge durations
Date: Sat, 30 Sep 2023 11:35:19 +0200 (CEST)
Message-ID: <47b96a8-db6b-aa20-d48-a6d60f0e84e@passwd.hu> (raw)
In-Reply-To: <20230929232001.23197-1-michael@niedermayer.cc>
On Sat, 30 Sep 2023, Michael Niedermayer wrote:
> Fixes: signed integer overflow: 109817402400 * 301990077 cannot be represented in type 'long long'
> Fixes: 51896/clusterfuzz-testcase-minimized-ffmpeg_dem_AVI_fuzzer-6706191715139584
>
> Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
> libavformat/avidec.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/avidec.c b/libavformat/avidec.c
> index 00bd7a98a9d..cfc693842b7 100644
> --- a/libavformat/avidec.c
> +++ b/libavformat/avidec.c
> @@ -27,6 +27,7 @@
> #include "libavutil/avstring.h"
> #include "libavutil/opt.h"
> #include "libavutil/dict.h"
> +#include "libavutil/integer.h"
> #include "libavutil/internal.h"
> #include "libavutil/intreadwrite.h"
> #include "libavutil/mathematics.h"
> @@ -476,7 +477,7 @@ static int calculate_bitrate(AVFormatContext *s)
> AVStream *st = s->streams[i];
> FFStream *const sti = ffstream(st);
> int64_t duration;
> - int64_t bitrate;
> + int64_t bitrate = 0;
>
> for (j = 0; j < sti->nb_index_entries; j++)
> len += sti->index_entries[j].size;
> @@ -484,7 +485,14 @@ static int calculate_bitrate(AVFormatContext *s)
> if (sti->nb_index_entries < 2 || st->codecpar->bit_rate > 0)
> continue;
> duration = sti->index_entries[j-1].timestamp - sti->index_entries[0].timestamp;
> - bitrate = av_rescale(8*len, st->time_base.den, duration * st->time_base.num);
> + if (INT64_MAX / duration >= st->time_base.num) {
> + bitrate = av_rescale(8*len, st->time_base.den, duration * st->time_base.num);
Why not always use the AVInteger version? This is not performance
sensitive as far as I see.
Regards,
Marton
> + } else {
> + AVInteger bitrate_i = av_div_i(av_mul_i(av_int2i(8*len), av_int2i(st->time_base.den)),
> + av_mul_i(av_int2i(duration), av_int2i(st->time_base.num)));
> + if (av_cmp_i(bitrate_i, av_int2i(INT64_MAX)) <= 0)
> + bitrate = av_i2int(bitrate_i);
> + }
> if (bitrate > 0) {
> st->codecpar->bit_rate = bitrate;
> }
> --
> 2.17.1
>
> _______________________________________________
> 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:[~2023-09-30 9:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 23:19 Michael Niedermayer
2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 2/6] avformat/avidec: Correct unsigend type Michael Niedermayer
2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 3/6] vformat/cafdec: dont seek beyond 64bit Michael Niedermayer
2023-09-29 23:19 ` [FFmpeg-devel] [PATCH 4/6] avformat/cafdec: saturate start + size into 64bit Michael Niedermayer
2023-09-29 23:41 ` James Almer
2023-09-30 16:32 ` Michael Niedermayer
2024-03-25 22:54 ` Michael Niedermayer
2023-09-29 23:20 ` [FFmpeg-devel] [PATCH 5/6] avformat/dxa: Adjust order of operations around block align Michael Niedermayer
2023-09-29 23:20 ` [FFmpeg-devel] [PATCH 6/6] avformat/iff: Saturate avio_tell() + 12 Michael Niedermayer
2024-03-25 22:58 ` Michael Niedermayer
2023-09-30 9:35 ` Marton Balint [this message]
2023-09-30 14:04 ` [FFmpeg-devel] [PATCH 1/6] avformat/avidec: support huge durations Michael Niedermayer
2023-09-30 14:31 ` Michael Niedermayer
2023-09-30 20:18 ` Anton Khirnov
2023-09-30 22:28 ` Michael Niedermayer
2023-10-02 9:07 ` Anton Khirnov
2023-10-02 19:03 ` Michael Niedermayer
2023-10-03 9:10 ` Tomas Härdin
2023-10-03 18:53 ` Michael Niedermayer
2024-03-25 22:50 ` Michael Niedermayer
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=47b96a8-db6b-aa20-d48-a6d60f0e84e@passwd.hu \
--to=cus@passwd.hu \
--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