Windows: correct pthread_xxx_init semantics
authorJeffrey Altman <jaltman@your-file-system.com>
Mon, 7 Feb 2011 21:44:09 +0000 (16:44 -0500)
committerJeffrey Altman <jaltman@openafs.org>
Tue, 8 Feb 2011 14:36:12 +0000 (06:36 -0800)
commitae11ef7898ecffe8eb2a38151602572c24e32a76
tree6f9103fe6b802dd4eb9d2fa17ecc8be8b52ad2ae
parent380cc22a45dff7e40cd50d57a56742b59ccc4952
Windows: correct pthread_xxx_init semantics

pthread lock and conditional initialization semantics
do not require that the lock structure be zeroed before
pthread_xxxx_init() functions are called.  Since the Windows
CriticalSection initialization does require that the memory
be zeroed, the pthread_xxxx_init() functions must zero the
memory just in case before performing the CriticalSection
initialization.

Change-Id: I61e78ca7cbc10f7d4144b8efcbb38f67bb8fd695
Reviewed-on: http://gerrit.openafs.org/3904
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Tested-by: Jeffrey Altman <jaltman@openafs.org>
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
src/WINNT/pthread/pthread.c