* clone() + glibc thread safe?
@ 2006-01-12 1:40 Russell Leighton
2006-01-12 7:28 ` Arjan van de Ven
0 siblings, 1 reply; 2+ messages in thread
From: Russell Leighton @ 2006-01-12 1:40 UTC (permalink / raw)
To: linux-kernel, libc-alpha
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
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: clone() + glibc thread safe?
2006-01-12 1:40 clone() + glibc thread safe? Russell Leighton
@ 2006-01-12 7:28 ` Arjan van de Ven
0 siblings, 0 replies; 2+ messages in thread
From: Arjan van de Ven @ 2006-01-12 7:28 UTC (permalink / raw)
To: Russell Leighton; +Cc: linux-kernel, libc-alpha
On Wed, 2006-01-11 at 20:40 -0500, Russell Leighton wrote:
> 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)
no
unless you tell glibc you're using threads (by using the glibc threading
primitives) glibc doesn't provide such thread safety.
(glibc at runtime knows you have threads and switches to thread-safe
operations)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-01-12 7:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-12 1:40 clone() + glibc thread safe? Russell Leighton
2006-01-12 7:28 ` Arjan van de Ven
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.