From: Dale Curtis <dalecurtis@chromium.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] Check codec_whitelist before reinitializing AVCtx.priv_data. Date: Wed, 31 Jul 2024 14:29:55 -0700 Message-ID: <CAPUDrwcPm4wGHVqBoP=pfXR+huKJyYhrM8dGoxokhXg+BgeRww@mail.gmail.com> (raw) In-Reply-To: <CAPUDrweh06ePsESg9AmTjji+rWD2+om9aazu5Pr6dBFx193+jQ@mail.gmail.com> On Wed, Jul 31, 2024 at 2:10 PM Dale Curtis <dalecurtis@chromium.org> wrote: > On Wed, Jul 31, 2024 at 4:32 AM Anton Khirnov <anton@khirnov.net> wrote: > >> Quoting Dale Curtis (2024-07-31 01:14:13) >> > I realized there are a couple more allocations that can be skipped here >> > when a codec is not on the allow list. Here's the updated patch. >> > >> > - dale >> > >> > On Mon, Jul 29, 2024 at 10:19 AM Dale Curtis <dalecurtis@chromium.org> >> > wrote: >> > >> > > This ensures that if a codec isn't on codec_whitelist, its VUI >> > > information can still be populated during find_stream_info() >> > > via parsers. >> > > >> > > Signed-off-by: Dale Curtis <dalecurtis@chromium.org> >> > > --- >> > > libavcodec/avcodec.c | 12 ++++++------ >> > > 1 file changed, 6 insertions(+), 6 deletions(-) >> > > >> > > >> > >> > From f87042d77d13c4c45f4b800146dc16347c1007d4 Mon Sep 17 00:00:00 2001 >> > From: Dale Curtis <dalecurtis@chromium.org> >> > Date: Tue, 30 Jul 2024 23:12:21 +0000 >> > Subject: [PATCH] Check codec_whitelist before reinitializing >> AVCtx.priv_data. >> > >> > This ensures that if a codec isn't on codec_whitelist, its VUI >> > information can still be populated during find_stream_info() >> > via parsers. >> >> Can you elaborate on this? >> > > The current code reinitializes the private data structures then checks the > whitelist. If the private data section had already been filled out, it ends > up being overwritten causing find_stream_info to drop side channel data. > > >> > >> > Signed-off-by: Dale Curtis <dalecurtis@chromium.org> >> > --- >> > libavcodec/avcodec.c | 11 +++++------ >> > 1 file changed, 5 insertions(+), 6 deletions(-) >> > >> > diff --git a/libavcodec/avcodec.c b/libavcodec/avcodec.c >> > index 214dca4566..1f9b3eb360 100644 >> > --- a/libavcodec/avcodec.c >> > +++ b/libavcodec/avcodec.c >> > @@ -174,6 +174,11 @@ int attribute_align_arg >> avcodec_open2(AVCodecContext *avctx, const AVCodec *code >> > if (avctx->extradata_size < 0 || avctx->extradata_size >= >> FF_MAX_EXTRADATA_SIZE) >> > return AVERROR(EINVAL); >> > >> > + if (avctx->codec_whitelist && av_match_list(codec->name, >> avctx->codec_whitelist, ',') <= 0) { >> > + av_log(avctx, AV_LOG_ERROR, "Codec (%s) not on whitelist >> \'%s\'\n", codec->name, avctx->codec_whitelist); >> > + return AVERROR(EINVAL); >> > + } >> >> I think this will break the case where the whitelist is provided in the >> options dictionary, as it's not applied yet at this point. >> > > I just copied the existing code a few lines up, so it seems ancillary to > this patch, but I can fix it in this one too if you want. > Nevermind, I see what you're saying -- yes this does break that case. Thanks for catching. I'll send a fix shortly. > > >> >> -- >> Anton Khirnov >> _______________________________________________ >> 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:[~2024-07-31 21:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-29 17:19 Dale Curtis 2024-07-30 23:14 ` Dale Curtis 2024-07-31 11:32 ` Anton Khirnov 2024-07-31 21:10 ` Dale Curtis 2024-07-31 21:29 ` Dale Curtis [this message] 2024-07-31 23:18 ` Dale Curtis 2024-08-14 16:44 ` Dale Curtis
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='CAPUDrwcPm4wGHVqBoP=pfXR+huKJyYhrM8dGoxokhXg+BgeRww@mail.gmail.com' \ --to=dalecurtis@chromium.org \ --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