Bug 20116: Clarify behaviour of PD->lock.

Add comments to the concurrency notes to clarify the semaphore-like and
mutex-like behaviours of PD->lock.

2 files changed, 18 insertions, 3 deletions

diff --git a/ChangeLog b/ChangeLog
index fa61e5fdb7..c2d13f1dc8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,10 @@
-2016-04-03  Adhemerval Zanella  <adhemerval.zanella@linaro.org>
+2017-05-03  Carlos O'Donell  <carlos@redhat.com>
+
+	[BZ #20116]
+	* nptl/pthread_create.c: Expand comments to describe
+	semaphore-like and mutex-like uses of PD->lock.
+
+2017-04-03  Adhemerval Zanella  <adhemerval.zanella@linaro.org>
 
 	* sysdeps/unix/sysv/linux/epoll_wait.c: New file.
 	* sysdeps/unix/sysv/linux/generic/epoll_wait.c: Remove file.
diff --git a/nptl/pthread_create.c b/nptl/pthread_create.c
index d0d74149d3..c7d1b8f413 100644
--- a/nptl/pthread_create.c
+++ b/nptl/pthread_create.c
@@ -94,8 +94,17 @@ unsigned int __nptl_nthreads = 1;
    exactly which of the four ownership states we are in and therefore
    what actions can be taken.  For example after (2) we cannot read or
    write from PD anymore since the thread may no longer exist and the
-   memory may be unmapped.  The most complicated cases happen during
-   thread startup:
+   memory may be unmapped.
+
+   It is important to point out that PD->lock is being used both
+   similar to a one-shot semaphore and subsequently as a mutex.  The
+   lock is taken in the parent to force the child to wait, and then the
+   child releases the lock.  However, this semaphore-like effect is used
+   only for synchronizing the parent and child.  After startup the lock
+   is used like a mutex to create a critical section during which a
+   single owner modifies the thread parameters.
+
+   The most complicated cases happen during thread startup:
 
    (a) If the created thread is in a detached (PTHREAD_CREATE_DETACHED),
        or joinable (default PTHREAD_CREATE_JOINABLE) state and