[Bug libc/5069] env thread safety problem

["zhangxiliang at cn dot fujitsu dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From zhangxiliang at cn dot fujitsu dot com  2007-09-26 08:11 -------
(In reply to comment #4)
> (In reply to comment #3)
> Hi everyone,
> 
> Does it take whether it is safety into consideration about the functions of 
> the following which is referring to __environ directly?
> 
> The exec*() family of functions, dlopen(), wordexp(), malloc(), and others 

These functions refer to __environ by calling the getenv(). They are safety
after applying the patch. Because the write lock can avoid the __environ changed
when calling getenv().

By the way, the read lock dosen't reduce the performance for get the env
variable operation.
All the functions (dlopen(), wordexp(), malloc(), and others) can achieve full
concurrency.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5069

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.