From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: Zane van Iperen <zane@zanevaniperen.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1] avformat/imf: fix CPL parsing error handling
Date: Tue, 4 Jan 2022 18:44:36 -0800
Message-ID: <CAF_7JxDDgXKngzXfGidHG25u45zOZqNn5bCJBguYY-FUemSzLA@mail.gmail.com> (raw)
In-Reply-To: <06b93b03-022b-4685-690d-5cda0dba9544@zanevaniperen.com>
On Tue, Jan 4, 2022 at 4:58 PM Zane van Iperen <zane@zanevaniperen.com> wrote:
>
>
>
> On 4/1/22 16:10, pal@sandflow.com wrote:
> > From: Pierre-Anthony Lemieux <pal@palemieux.com>
> >
> > Signed-off-by: Pierre-Anthony Lemieux <pal@palemieux.com>
> > ---
> > libavformat/imf_cpl.c | 51 +++++++++++++++++++++++--------------------
> > 1 file changed, 27 insertions(+), 24 deletions(-)
>
> Could you please resend this as two separate commits? One with the change, one
> with the re-indenting? It makes it easier to review (and bisect) in the future.
Ok. Got it. See v2 at:
http://ffmpeg.org/pipermail/ffmpeg-devel/2022-January/290840.html
>
> For reference, the effective change is:
>
> diff --git a/libavformat/imf_cpl.c b/libavformat/imf_cpl.c
> index 28798d3e36..366a1be9e2 100644
> --- a/libavformat/imf_cpl.c
> +++ b/libavformat/imf_cpl.c
> @@ -807,7 +807,9 @@ int ff_imf_parse_cpl(AVIOContext *in, FFIMFCPL **cpl)
> av_log(NULL, AV_LOG_ERROR, "Cannot read IMF CPL\n");
> if (ret == 0)
> ret = AVERROR_INVALIDDATA;
> - } else {
> + goto clean_up;
> + }
> +
> LIBXML_TEST_VERSION
>
> filesize = buf.len;
> @@ -817,6 +819,7 @@ int ff_imf_parse_cpl(AVIOContext *in, FFIMFCPL **cpl)
> AV_LOG_ERROR,
> "XML parsing failed when reading the IMF CPL\n");
> ret = AVERROR_INVALIDDATA;
> + goto clean_up;
> }
>
> if ((ret = ff_imf_parse_cpl_from_xml_dom(doc, cpl))) {
> @@ -833,8 +836,8 @@ int ff_imf_parse_cpl(AVIOContext *in, FFIMFCPL **cpl)
> }
>
> xmlFreeDoc(doc);
> - }
>
> +clean_up:
> av_bprint_finalize(&buf, NULL);
>
> return ret;
>
>
> > + av_log(NULL,
> > + AV_LOG_INFO,
> > + "IMF CPL Id: " FF_IMF_UUID_FORMAT "\n",
> > + UID_ARG((*cpl)->id_uuid));
> > + }
> > +
> > + xmlFreeDoc(doc);
> > +
>
> Trailing whitespace here.
>
>
_______________________________________________
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:[~2022-01-05 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 6:10 pal
2022-01-05 0:58 ` Zane van Iperen
2022-01-05 2:44 ` Pierre-Anthony Lemieux [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=CAF_7JxDDgXKngzXfGidHG25u45zOZqNn5bCJBguYY-FUemSzLA@mail.gmail.com \
--to=pal@sandflow.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=zane@zanevaniperen.com \
/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