From: Vignesh Venkatasubramanian <vigneshv-at-google.com@ffmpeg.org>
To: Michael Niedermayer <michael@niedermayer.cc>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 3/5] avformat/mov: Better check for duplicate iloc
Date: Tue, 25 Apr 2023 15:22:50 -0700
Message-ID: <CAOJaEP+cNHtuU8VZ=pRPigppc0xJRMW_s2v3d7n63LYw_BFbgQ@mail.gmail.com> (raw)
In-Reply-To: <20230417231820.GM275832@pb2>
On Mon, Apr 17, 2023 at 4:18 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> On Mon, Apr 17, 2023 at 12:36:26PM +0200, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2023-04-17 00:25:16)
> > > Fixes: memleak
> > > Fixes: 45982/clusterfuzz-testcase-minimized-ffmpeg_DEMUXER_fuzzer-6674082962997248
> > >
> > > Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> > > ---
> > > libavformat/mov.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/libavformat/mov.c b/libavformat/mov.c
> > > index 057fd872b10..6853bb324cf 100644
> > > --- a/libavformat/mov.c
> > > +++ b/libavformat/mov.c
> > > @@ -7777,7 +7777,7 @@ static int mov_read_iloc(MOVContext *c, AVIOContext *pb, MOVAtom atom)
> > > return 0;
> > > }
> > >
> > > - if (c->fc->nb_streams) {
> > > + if (c->fc->nb_streams || c->avif_info) {
> >
> > This first condition is now redundant, is it not?
>
> Iam not sure
I think the second condition alone should be enough here. Either way,
lgtm (if the current patch is more clearer for readers).
> what exactly happens if a trak occurs before
>
If a trak occurs before, then the condition in the line above should
take care of that case (!c->is_still_picture_avif). Because if a trak
was found, it will not be considered a still picture.
> Iam also not sure what happens if multiple meta tags occur triggering
> the avif stream addition, i may be missing something but the code seems
> not to expect that
>
Multiple meta tags are not allowed in the AVIF/HEIF specification.
> Adding the author of this code to CC
>
> thx
>
> [...]
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> In a rich man's house there is no place to spit but his face.
> -- Diogenes of Sinope
--
Vignesh
_______________________________________________
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 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 22:25 [FFmpeg-devel] [PATCH 1/5] avcodec/pcm_rechunk_bsf: unref packet before putting a new one in Michael Niedermayer
2023-04-16 22:25 ` [FFmpeg-devel] [PATCH 2/5] avformat/avs: unref packet after avs_read_audio_packet() fail Michael Niedermayer
2023-04-16 22:25 ` [FFmpeg-devel] [PATCH 3/5] avformat/mov: Better check for duplicate iloc Michael Niedermayer
2023-04-17 10:36 ` Anton Khirnov
2023-04-17 23:18 ` Michael Niedermayer
2023-04-25 22:22 ` Vignesh Venkatasubramanian [this message]
2023-09-29 19:21 ` Michael Niedermayer
2023-10-03 22:56 ` Vignesh Venkat via ffmpeg-devel
2023-10-04 4:22 ` Vignesh Venkat via ffmpeg-devel
2023-04-16 22:25 ` [FFmpeg-devel] [PATCH 4/5] avcodec/hevc_ps: Use get_ue_golomb() instead of get_ue_golomb_long() for depth Michael Niedermayer
2023-04-16 22:25 ` [FFmpeg-devel] [PATCH 5/5] avcodec/hevc_ps: Check depth to be within 8 to 16 Michael Niedermayer
2023-04-30 22:32 ` Michael Niedermayer
2023-04-16 22:57 ` [FFmpeg-devel] [PATCH 1/5] avcodec/pcm_rechunk_bsf: unref packet before putting a new one in James Almer
2023-04-17 11:26 ` Michael Niedermayer
2023-04-17 11:28 ` James Almer
2023-04-17 11:34 ` Michael Niedermayer
2023-04-17 17:13 ` Marton Balint
2023-04-17 17:23 ` 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='CAOJaEP+cNHtuU8VZ=pRPigppc0xJRMW_s2v3d7n63LYw_BFbgQ@mail.gmail.com' \
--to=vigneshv-at-google.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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