From: Steven Liu <lq@chinaffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Steven Liu <lq@chinaffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/libsrt: use a larger buffer for find_info_tag Date: Wed, 30 Mar 2022 10:31:44 +0800 Message-ID: <9241007A-E7F6-4D44-8747-1C36DA0FE205@chinaffmpeg.org> (raw) In-Reply-To: <CACYjbn1Qu6qzUgZgRRAgSHWWUqz1qDKF5r2oM7O2KveU4AXbEA@mail.gmail.com> > 2022年3月29日 下午2:11,mypopy@gmail.com 写道: > > On Tue, Mar 29, 2022 at 10:21 AM "zhilizhao(赵志立)" > <quinkblack@foxmail.com> wrote: >> >> Ping. >> >>> On Aug 14, 2021, at 6:43 PM, Zhao Zhili <quinkblack@foxmail.com> wrote: >>> >>> The upper limit of strlen(streamid) is 512. Use a larger buffer for >>> future proof, for example, deal with percent-encoding. >>> --- >>> libavformat/libsrt.c | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/libavformat/libsrt.c b/libavformat/libsrt.c >>> index e5701625b8..a66c85d3a2 100644 >>> --- a/libavformat/libsrt.c >>> +++ b/libavformat/libsrt.c >>> @@ -513,7 +513,7 @@ static int libsrt_open(URLContext *h, const char *uri, int flags) >>> { >>> SRTContext *s = h->priv_data; >>> const char * p; >>> - char buf[256]; >>> + char buf[1024]; >>> int ret = 0; >>> >>> if (srt_startup() < 0) { >>> -- >>> 2.31.1 > > LGTM, thx Applied as 3721aaeaaae9f817abb843117ae8dae1dc280a7f > _______________________________________________ > 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". Thanks Steven Liu _______________________________________________ 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-03-30 2:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <tencent_2A522DEA9A2340B19A6C9F62ABA44E957008@qq.com> 2022-03-29 2:21 ` "zhilizhao(赵志立)" 2022-03-29 6:11 ` mypopy 2022-03-30 2:31 ` Steven Liu [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=9241007A-E7F6-4D44-8747-1C36DA0FE205@chinaffmpeg.org \ --to=lq@chinaffmpeg.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