From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: metamuffin <metamuffin@disroot.org> Subject: Re: [FFmpeg-devel] [PATCH] avdevice/lavfi: fix crash on unconnected outpads Date: Thu, 1 Jun 2023 23:40:14 +0200 Message-ID: <CAPYw7P752898qngvdNd0Ga+9hyh0RXmtty0eCLcOWhr2Ssu36g@mail.gmail.com> (raw) In-Reply-To: <20230601101336.24053-1-metamuffin@disroot.org> On Thu, Jun 1, 2023 at 12:14 PM metamuffin <metamuffin@disroot.org> wrote: > Nameless outpads would cause an invocation to sscanf with NULL. > Example: ffmpeg -f lavfi -i 'nullsrc;nullsrc' - > Changed to throwing an error instead. > See: https://git.videolan.org/?p=ffmpeg.git;a=commit;h=5ce76506de1a7fbaf91af47a925d5ecfe13ae59c Perhaps needs backporting to first introduction. > --- > libavdevice/lavfi.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/libavdevice/lavfi.c b/libavdevice/lavfi.c > index 9c1fcf334b..21f33ade0e 100644 > --- a/libavdevice/lavfi.c > +++ b/libavdevice/lavfi.c > @@ -174,6 +174,11 @@ av_cold static int lavfi_read_header(AVFormatContext > *avctx) > * create a mapping between them and the streams */ > for (i = 0, inout = output_links; inout; i++, inout = inout->next) { > int stream_idx = 0, suffix = 0, use_subcc = 0; > + if (!inout->name) { > + av_log(avctx, AV_LOG_ERROR, > + "Filtergraph has nameless outpads\n"); > + FAIL(AVERROR(EINVAL)); > + } > sscanf(inout->name, "out%n%d%n", &suffix, &stream_idx, &suffix); > if (!suffix) { > av_log(avctx, AV_LOG_ERROR, > -- > 2.40.1 > > _______________________________________________ > 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:[~2023-06-01 21:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 10:13 metamuffin 2023-06-01 21:40 ` Paul B Mahol [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-05-07 10:34 metamuffin
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=CAPYw7P752898qngvdNd0Ga+9hyh0RXmtty0eCLcOWhr2Ssu36g@mail.gmail.com \ --to=onemda@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=metamuffin@disroot.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