mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Cc: rebecca.zhang.cn@windriver.com, wenbin.deng.cn@windriver.com
Subject: Re: [PATCH] __libc_exit_fini forgets to do pthread_mutex_unlock
Date: Wed, 2 Jul 2025 06:30:33 +0200	[thread overview]
Message-ID: <aGS1zWJgC6yl4qP0@voyager> (raw)
In-Reply-To: <20250702022854.30301-1-rebecca.zhang.cn@windriver.com>

Am Wed, Jul 02, 2025 at 10:28:54AM +0800 schrieb rebecca.zhang.cn@windriver.com:
> From: Rebecca Zhang <rebecca.zhang.cn@windriver.com>
> 
> This commit fixes the issue that __libc_exit_fini only do
> pthread_mutex_lock, but forget to do pthread_mutex_unlock.
> ---
>  ldso/dynlink.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/ldso/dynlink.c b/ldso/dynlink.c
> index ceca3c9..7885675 100644
> --- a/ldso/dynlink.c
> +++ b/ldso/dynlink.c
> @@ -1492,6 +1492,7 @@ void __libc_exit_fini()
>  			fpaddr(p, dyn[DT_FINI])();
>  #endif
>  	}
> +	pthread_mutex_unlock(&init_fini_lock);
>  }
>  
>  void __ldso_atfork(int who)
> -- 
> 2.34.1
> 
I think that is a deliberate omision. __libc_exit_fini() is called on
process exit. After it runs, it must not run again, and no new
initializer must run at all. The process will exit very soon anyway. The
only way to deadlock here is if a destructor calls exit(), which they
aren't allowed to do.

Ciao,
Markus


  reply	other threads:[~2025-07-02  4:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  2:28 [PATCH] __libc_exit_fini forgets to do pthread_mutex_unlock rebecca.zhang.cn
2025-07-02  4:30 ` Markus Wichmann [this message]
2025-07-02  6:06   ` [musl] " Zhang, Huilin (Rebecca) (CN)
2025-07-02  6:20     ` Deng, Wenbin (CN)
2025-07-02 14:18     ` Rich Felker
2025-07-02 14:33   ` Rich Felker
2025-07-03  1:44     ` Zhang, Huilin (Rebecca) (CN)

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=aGS1zWJgC6yl4qP0@voyager \
    --to=nullplan@gmx.net \
    --cc=musl@lists.openwall.com \
    --cc=rebecca.zhang.cn@windriver.com \
    --cc=wenbin.deng.cn@windriver.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).