[RFC]setlocale() race condition

[Carlos O'Donell]

On Fri, Jun 13, 2008 at 1:43 AM, Sharyathi Nagesh <sharyath@in.ibm.com> wrote:
> So can access to this global variable made thread safe even if function is
> not re-enterant

Yes, access to the global variable *can* be made thread-safe (even
though the function is not re-entrant due specifically to the use of a
global variable).

It would be best if you found a URL reference for the section quoted
by Mark Brown regarding thread-safety. I assume Mark is talking about
this:

http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html
~~~
Section 2.9.1 Thread Safety
All functions defined by this volume of IEEE Std 1003.1-2001 shall be
thread-safe, except that the following functions1 need not be
thread-safe.
~~~

This is the type of rationale you need put forward to get your patches
accepted, along with the contribution checklist
http://sourceware.org/glibc/wiki/Contribution%20checklist

Cheers,
Carlos.