From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] MT fork and key_lock in pthread_key_create.c
Date: Fri, 7 Oct 2022 21:36:16 -0400 [thread overview]
Message-ID: <20221008013615.GE29905@brightrain.aerifal.cx> (raw)
In-Reply-To: <20221006182151.GV29905@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Thu, Oct 06, 2022 at 02:21:51PM -0400, Rich Felker wrote:
> On Thu, Oct 06, 2022 at 09:37:50AM +0300, Alexey Izbyshev wrote:
> > Hi,
> >
> > I noticed that fork() doesn't take key_lock that is used to protect
> > the global table of thread-specific keys. I couldn't find mentions
> > of this lock in the MT fork discussion in the mailing list archive.
> > Was this lock overlooked?
>
> I think what happened was that we made the main list of locks to
> review and take care of via grep for LOCK, and then manually added
> known instances of locks using other locking primitives. This one must
> have been missed.
>
> Having special-case lock types like this is kinda a pain, but as long
> as there aren't too many I guess it's not a big deal.
Proposed patch attached.
[-- Attachment #2: pthread_key_fork.diff --]
[-- Type: text/plain, Size: 2004 bytes --]
diff --git a/src/internal/fork_impl.h b/src/internal/fork_impl.h
index ae3a79e5..354e733b 100644
--- a/src/internal/fork_impl.h
+++ b/src/internal/fork_impl.h
@@ -16,3 +16,4 @@ extern hidden volatile int *const __vmlock_lockptr;
hidden void __malloc_atfork(int);
hidden void __ldso_atfork(int);
+hidden void __pthread_key_atfork(int);
diff --git a/src/process/fork.c b/src/process/fork.c
index 80e804b1..56f19313 100644
--- a/src/process/fork.c
+++ b/src/process/fork.c
@@ -37,6 +37,7 @@ static void dummy(int x) { }
weak_alias(dummy, __fork_handler);
weak_alias(dummy, __malloc_atfork);
weak_alias(dummy, __aio_atfork);
+weak_alias(dummy, __pthread_key_atfork);
weak_alias(dummy, __ldso_atfork);
static void dummy_0(void) { }
@@ -51,6 +52,7 @@ pid_t fork(void)
int need_locks = libc.need_locks > 0;
if (need_locks) {
__ldso_atfork(-1);
+ __pthread_key_atfork(-1);
__aio_atfork(-1);
__inhibit_ptc();
for (int i=0; i<sizeof atfork_locks/sizeof *atfork_locks; i++)
@@ -78,6 +80,7 @@ pid_t fork(void)
else **atfork_locks[i] = 0;
__release_ptc();
if (ret) __aio_atfork(0);
+ __pthread_key_atfork(!ret);
__ldso_atfork(!ret);
}
__restore_sigs(&set);
diff --git a/src/thread/pthread_key_create.c b/src/thread/pthread_key_create.c
index d1120941..39770c7a 100644
--- a/src/thread/pthread_key_create.c
+++ b/src/thread/pthread_key_create.c
@@ -1,4 +1,5 @@
#include "pthread_impl.h"
+#include "fork_impl.h"
volatile size_t __pthread_tsd_size = sizeof(void *) * PTHREAD_KEYS_MAX;
void *__pthread_tsd_main[PTHREAD_KEYS_MAX] = { 0 };
@@ -20,6 +21,13 @@ static void dummy_0(void)
weak_alias(dummy_0, __tl_lock);
weak_alias(dummy_0, __tl_unlock);
+void __pthread_key_atfork(int who)
+{
+ if (who<0) __pthread_rwlock_rdlock(&key_lock);
+ else if (!who) __pthread_rwlock_unlock(&key_lock);
+ else key_lock = (pthread_rwlock_t)PTHREAD_RWLOCK_INITIALIZER;
+}
+
int __pthread_key_create(pthread_key_t *k, void (*dtor)(void *))
{
pthread_t self = __pthread_self();
next prev parent reply other threads:[~2022-10-08 1:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 6:37 Alexey Izbyshev
2022-10-06 7:02 ` [musl] " Alexey Izbyshev
2022-10-06 19:20 ` Rich Felker
2022-10-06 19:50 ` Rich Felker
2022-10-07 1:26 ` Rich Felker
2022-10-07 10:53 ` Alexey Izbyshev
2022-10-07 21:18 ` Rich Felker
2022-10-08 16:07 ` Alexey Izbyshev
2022-10-07 8:18 ` Alexey Izbyshev
2022-10-06 20:04 ` Jeffrey Walton
2022-10-06 20:09 ` Rich Felker
2022-10-06 18:21 ` [musl] " Rich Felker
2022-10-08 1:36 ` Rich Felker [this message]
2022-10-08 17:03 ` Alexey Izbyshev
2022-10-11 17:50 ` Rich Felker
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=20221008013615.GE29905@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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).