From: Kacper Michajlow <kasper93@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: fix eof check after avio_skip()
Date: Mon, 3 Feb 2025 06:28:14 +0100
Message-ID: <CABPLASS1cv_z4kXpRZ46dKoUB0Bp94G7XA+B75wGfbok7-eovA@mail.gmail.com> (raw)
In-Reply-To: <20250203052335.413-1-kasper93@gmail.com>
On Mon, 3 Feb 2025 at 06:24, Kacper Michajłow <kasper93@gmail.com> wrote:
>
> This fix ensures that the loop stops early on EOF. The issue occurs
> because mov_read_infe() performs a version check and skips unsupported
> versions. The problem is that seeking within the stream clears the EOF
> flag, causing avio_feof() to not function as expected. This is resolved
> by moving the EOF check after reading the size and type after seek,
> ensuring the EOF flag is set when necessary.
>
> Signed-off-by: Kacper Michajłow <kasper93@gmail.com>
> ---
> libavformat/mov.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index 2c8be51063..9a388bf723 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -8868,12 +8868,12 @@ static int mov_read_iinf(MOVContext *c, AVIOContext *pb, MOVAtom atom)
> for (i = 0; i < entry_count; i++) {
> MOVAtom infe;
>
> + infe.size = avio_rb32(pb) - 8;
> + infe.type = avio_rl32(pb);
> if (avio_feof(pb)) {
> ret = AVERROR_INVALIDDATA;
> goto fail;
> }
> - infe.size = avio_rb32(pb) - 8;
> - infe.type = avio_rl32(pb);
> ret = mov_read_infe(c, pb, infe, i);
> if (ret < 0)
> goto fail;
> --
> 2.45.1
>
Sorry, sent the wrong patch, consider v2, with commit title fix.
- Kacper
_______________________________________________
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:[~2025-02-03 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 5:23 Kacper Michajłow
2025-02-03 5:28 ` Kacper Michajlow [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=CABPLASS1cv_z4kXpRZ46dKoUB0Bp94G7XA+B75wGfbok7-eovA@mail.gmail.com \
--to=kasper93@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