From: Russell Leighton <russ@elegant-software.com>
To: linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com
Subject: clone() + glibc thread safe?
Date: Wed, 11 Jan 2006 20:40:35 -0500 [thread overview]
Message-ID: <43C5B393.1010600@elegant-software.com> (raw)
Can you safely use glibc functions in a thread safe way (e.g., malloc()
and friends) from threads generated by:
clone(f, stack, CLONE_FS|CLONE_FILES|CLONE_VM, t)
Thx
Russ
next reply other threads:[~2006-01-12 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 1:40 Russell Leighton [this message]
2006-01-12 7:28 ` clone() + glibc thread safe? Arjan van de Ven
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=43C5B393.1010600@elegant-software.com \
--to=russ@elegant-software.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox