From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] avformat/mov: Don't use entry[-1] in pointer arithmetic
Date: Mon, 26 Feb 2024 19:28:11 -0300
Message-ID: <0c637d91-5d88-4567-9d4b-3f2cce2ffd1c@gmail.com> (raw)
In-Reply-To: <AS8P250MB0744EFFDD33DAD5A9A8DDBC78F5A2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
On 2/26/2024 7:15 PM, Andreas Rheinhardt wrote:
> It is undefined behaviour.
> Fixes many failed tests with UBSan and GCC 13 like
> "src/libavformat/mov.c:4229:44: runtime error: store to address
> 0x5572abe20f80 with insufficient space for an object of type 'struct
> MOVIndexRange'"
> (The line number does not refer to the line where &entry[-1]
> is assigned.)
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> Now switching to next_index_range in order to avoid
> having to duplicate the current_index_range == NULL check.
I prefer the first version. mov_fix_index() is called once per track
during init (and then it may not be called depending on user options),
so it's hardly a bottleneck, and next_index_range[-1] is much less clear
and intuitive at a quick glance than current_index_range.
>
> libavformat/mov.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index 71e8f7ae8f..d7da19998b 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -4022,7 +4022,7 @@ static void mov_fix_index(MOVContext *mov, AVStream *st)
> int num_discarded_begin = 0;
> int first_non_zero_audio_edit = -1;
> int packet_skip_samples = 0;
> - MOVIndexRange *current_index_range;
> + MOVIndexRange *next_index_range;
> int found_keyframe_after_edit = 0;
> int found_non_empty_edit = 0;
>
> @@ -4038,7 +4038,7 @@ static void mov_fix_index(MOVContext *mov, AVStream *st)
> return;
> }
> msc->current_index_range = msc->index_ranges;
> - current_index_range = msc->index_ranges - 1;
> + next_index_range = msc->index_ranges;
>
> // Clean AVStream from traces of old index
> sti->index_entries = NULL;
> @@ -4225,11 +4225,11 @@ static void mov_fix_index(MOVContext *mov, AVStream *st)
> }
>
> // Update the index ranges array
> - if (current_index_range < msc->index_ranges || index != current_index_range->end) {
> - current_index_range++;
> - current_index_range->start = index;
> + if (next_index_range == msc->index_ranges || index != next_index_range[-1].end) {
> + next_index_range->start = index;
> + next_index_range++;
> }
> - current_index_range->end = index + 1;
> + next_index_range[-1].end = index + 1;
>
> // Only start incrementing DTS in frame_duration amounts, when we encounter a frame in edit list.
> if (edit_list_start_encountered > 0) {
> @@ -4289,9 +4289,8 @@ static void mov_fix_index(MOVContext *mov, AVStream *st)
> av_freep(&frame_duration_buffer);
>
> // Null terminate the index ranges array
> - current_index_range++;
> - current_index_range->start = 0;
> - current_index_range->end = 0;
> + next_index_range->start = 0;
> + next_index_range->end = 0;
> msc->current_index = msc->index_ranges[0].start;
> }
>
_______________________________________________
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:[~2024-02-26 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 22:11 [FFmpeg-devel] [PATCH v2 1/2] Revert "avformat/mov: zero initialize the index ranges buffer" Andreas Rheinhardt
2024-02-26 22:12 ` James Almer
2024-02-26 22:15 ` [FFmpeg-devel] [PATCH v2 2/2] avformat/mov: Don't use entry[-1] in pointer arithmetic Andreas Rheinhardt
2024-02-26 22:28 ` James Almer [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=0c637d91-5d88-4567-9d4b-3f2cce2ffd1c@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