From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Zhao Zhili <zhilizhao@tencent.com> Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] avutil/executor: Fix stack overflow due to recursive call Date: Mon, 8 Jul 2024 21:24:15 +0800 Message-ID: <CAFXK13ff6JotFXGvxZ1YSAN8+0dbCt0Sui0616nE4CovckfVcg@mail.gmail.com> (raw) In-Reply-To: <tencent_1E40EB9A5E9F71AB484E9270382D3E9A1B08@qq.com> On Mon, Jul 8, 2024 at 8:14 PM Zhao Zhili <quinkblack@foxmail.com> wrote: > From: Zhao Zhili <zhilizhao@tencent.com> > > av_executor_execute run the task directly when thread is disabled. > The task can schedule a new task by call av_executor_execute. This > forms an implicit recursive call. This patch removed the recursive > call. > Thank you, Zhili. LGTM Using bool is a good idea. We could also use bool for has_lock, has_cond, and die. > --- > v2: use bool type > > libavutil/executor.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/libavutil/executor.c b/libavutil/executor.c > index 89058fab2f..bfce2ac444 100644 > --- a/libavutil/executor.c > +++ b/libavutil/executor.c > @@ -20,6 +20,8 @@ > > #include "config.h" > > +#include <stdbool.h> > + > #include "mem.h" > #include "thread.h" > > @@ -49,6 +51,7 @@ typedef struct ThreadInfo { > struct AVExecutor { > AVTaskCallbacks cb; > int thread_count; > + bool recursive; > > ThreadInfo *threads; > uint8_t *local_contexts; > @@ -207,8 +210,12 @@ void av_executor_execute(AVExecutor *e, AVTask *t) > } > > if (!e->thread_count || !HAVE_THREADS) { > + if (e->recursive) > + return; > + e->recursive = true; > // We are running in a single-threaded environment, so we must > handle all tasks ourselves > while (run_one_task(e, e->local_contexts)) > /* nothing */; > + e->recursive = false; > } > } > -- > 2.42.0 > > _______________________________________________ > 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".
prev parent reply other threads:[~2024-07-08 13:24 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-08 12:13 Zhao Zhili 2024-07-08 13:24 ` Nuo Mi [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=CAFXK13ff6JotFXGvxZ1YSAN8+0dbCt0Sui0616nE4CovckfVcg@mail.gmail.com \ --to=nuomi2021@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=zhilizhao@tencent.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