clone() + glibc thread safe?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: [email protected], [email protected]
Subject: clone() + glibc thread safe?
From: Russell Leighton <[email protected]>
Date: Wed, 11 Jan 2006 20:40:35 -0500
Sender: [email protected]
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: clone() + glibc thread safe?
  - From: Arjan van de Ven <[email protected]>

Prev by Date: Re: + add-pselect-ppoll-system-call-implementation-tidy.patch added to -mm tree
Next by Date: Re: + add-pselect-ppoll-system-call-implementation-tidy.patch added to -mm tree
Previous by thread: Re: + add-pselect-ppoll-system-call-implementation-tidy.patch added to -mm tree
Next by thread: Re: clone() + glibc thread safe?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]

Powered by Linux