From: Zhao Zhili <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avutil/executor: Fix missing check before using mutex Date: Mon, 1 Jul 2024 21:59:50 +0800 Message-ID: <tencent_206B1E7CCAAD1A394DC2A1B40069A601FD0A@qq.com> (raw) In-Reply-To: <CAFXK13fagusw05OwXsPAag4KwKmQ=0rrJuWmKqkHPUseB4Ef8A@mail.gmail.com> > On Jul 1, 2024, at 21:14, Nuo Mi <nuomi2021@gmail.com> wrote: > > On Sun, Jun 30, 2024 at 6:45 PM Zhao Zhili <quinkblack@foxmail.com> wrote: > >> From: Zhao Zhili <zhilizhao@tencent.com> >> >> --- >> The code can be simplified by always creating mutex/cond. I'm not sure >> it worth the overhead. Please note !HAVE_THREADS don't have the same >> problem since it has mock implementation of ff_mutex_lock/unlock. >> > Hi Zhili, > Thank you for the patch. > Do we really need this? The lock/unlock/signal functions will return an > error if the lock and condition variables are not initialized. We have strict check in libavutil/thread.h, e.g., static inline int strict_pthread_mutex_lock(pthread_mutex_t *mutex) { ASSERT_PTHREAD(pthread_mutex_lock, mutex); } The strict check is enabled when configure --assert-level=2. > >> >> libavutil/executor.c | 9 ++++++--- >> 1 file changed, 6 insertions(+), 3 deletions(-) >> >> diff --git a/libavutil/executor.c b/libavutil/executor.c >> index fb20104b58..89058fab2f 100644 >> --- a/libavutil/executor.c >> +++ b/libavutil/executor.c >> @@ -194,14 +194,17 @@ void av_executor_execute(AVExecutor *e, AVTask *t) >> AVTaskCallbacks *cb = &e->cb; >> AVTask **prev; >> >> - ff_mutex_lock(&e->lock); >> + if (e->thread_count) >> + ff_mutex_lock(&e->lock); >> if (t) { >> for (prev = &e->tasks; *prev && cb->priority_higher(*prev, t); >> prev = &(*prev)->next) >> /* nothing */; >> add_task(prev, t); >> } >> - ff_cond_signal(&e->cond); >> - ff_mutex_unlock(&e->lock); >> + if (e->thread_count) { >> + ff_cond_signal(&e->cond); >> + ff_mutex_unlock(&e->lock); >> + } >> >> if (!e->thread_count || !HAVE_THREADS) { >> // We are running in a single-threaded environment, so we must >> handle all tasks ourselves >> -- >> 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". _______________________________________________ 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-01 14:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-30 10:45 Zhao Zhili 2024-07-01 13:14 ` Nuo Mi 2024-07-01 13:59 ` Zhao Zhili [this message] 2024-07-01 14:13 ` Nuo Mi 2024-07-11 12:33 ` Nuo Mi
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=tencent_206B1E7CCAAD1A394DC2A1B40069A601FD0A@qq.com \ --to=quinkblack@foxmail.com \ --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