From: "Appelmans, Madeleine" <madelea@amazon.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: [musl] Difference in pthread behavior between glibc and musl
Date: Tue, 11 Jul 2023 19:19:50 +0000 [thread overview]
Message-ID: <D05988EE-5C2C-4893-ABA8-F35570CD83C7@amazon.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 818 bytes --]
Hello,
There seems to be a difference in pthread behavior when compiling with glibc and using the musl-gcc wrapper. The attached snippet of code creates a destructor attribute which deletes a pthread key. The code never actually creates the pthread key. This code segfaults when compiled using musl-gcc, and does not segfault when compiled with gcc.
Best guess at what is going on: When creating a pthread key, musl initializes a field called tsd<https://git.musl-libc.org/cgit/musl/tree/src/thread/pthread_key_create.c#n37>. When deleting a key, musl assumes that initialization has been done, and dereferences tsd without checking that it exists: see here<https://git.musl-libc.org/cgit/musl/tree/src/thread/pthread_key_create.c#n65>. This dereference may be the source of the segfault.
Thanks,
Madeleine
[-- Attachment #1.2: Type: text/html, Size: 2894 bytes --]
[-- Attachment #2: pthread_test.c --]
[-- Type: application/octet-stream, Size: 217 bytes --]
#include <pthread.h>
static pthread_key_t per_thread_key;
static void __attribute__((destructor)) key_cleanup(void)
{
pthread_key_delete(per_thread_key);
}
int main(int argc, char **argv)
{
// Do nothing
}
next reply other threads:[~2023-07-11 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 19:19 Appelmans, Madeleine [this message]
2023-07-11 19:42 ` Markus Wichmann
2023-07-12 2:48 ` Rich Felker
2023-07-13 1:00 ` Gabriel Ravier
2023-07-13 1:50 ` Rich Felker
2023-07-13 2:02 ` Gabriel Ravier
2023-07-13 16:27 ` Markus Wichmann
2023-07-13 18:49 ` Gabriel Ravier
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=D05988EE-5C2C-4893-ABA8-F35570CD83C7@amazon.com \
--to=madelea@amazon.com \
--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).