diff options
| author | joseph <joseph@7b3dc134-2b1b-0410-93df-9e9f96275f8d> | 2009-11-11 01:01:35 +0000 |
|---|---|---|
| committer | joseph <joseph@7b3dc134-2b1b-0410-93df-9e9f96275f8d> | 2009-11-11 01:01:35 +0000 |
| commit | 85437c7924a18e38c94912459fde243ff9a30923 (patch) | |
| tree | 3bdead09c8838b22dd0e5a88698c22a7d10481f7 /linuxthreads | |
| parent | dd67338f78d03d7cad1ce5342227c86f1d7f32bb (diff) | |
2009-11-10 Samuel Thibault <samuel.thibault@ens-lyon.org>
* man/pthread_mutex_init.man: Document that recursive mutexes
check that the caller is the owner of the lock.
git-svn-id: svn://svn.eglibc.org/trunk@9218 7b3dc134-2b1b-0410-93df-9e9f96275f8d
Diffstat (limited to 'linuxthreads')
| -rw-r--r-- | linuxthreads/linuxthreads/ChangeLog.eglibc | 9 | ||||
| -rw-r--r-- | linuxthreads/linuxthreads/man/pthread_mutex_init.man | 16 |
2 files changed, 17 insertions, 8 deletions
diff --git a/linuxthreads/linuxthreads/ChangeLog.eglibc b/linuxthreads/linuxthreads/ChangeLog.eglibc new file mode 100644 index 000000000..4b96793d1 --- /dev/null +++ b/linuxthreads/linuxthreads/ChangeLog.eglibc @@ -0,0 +1,9 @@ +2009-11-10 Samuel Thibault <samuel.thibault@ens-lyon.org> + + * man/pthread_mutex_init.man: Document that recursive mutexes + check that the caller is the owner of the lock. + +Local Variables: +mode: change-log +change-log-default-name: "ChangeLog.eglibc" +End: diff --git a/linuxthreads/linuxthreads/man/pthread_mutex_init.man b/linuxthreads/linuxthreads/man/pthread_mutex_init.man index 643b007ae..a0bed5f0d 100644 --- a/linuxthreads/linuxthreads/man/pthread_mutex_init.man +++ b/linuxthreads/linuxthreads/man/pthread_mutex_init.man @@ -88,14 +88,14 @@ mutex (number of !pthread_mutex_lock! operations performed on it by the calling thread), and only when this count reaches zero is the mutex actually unlocked. -On ``error checking'' mutexes, !pthread_mutex_unlock! actually checks -at run-time that the mutex is locked on entrance, and that it was -locked by the same thread that is now calling !pthread_mutex_unlock!. -If these conditions are not met, an error code is returned and the -mutex remains unchanged. ``Fast'' and ``recursive'' mutexes perform -no such checks, thus allowing a locked mutex to be unlocked by a -thread other than its owner. This is non-portable behavior and must -not be relied upon. +On ``error checking'' and ``recursive'' mutexes, +!pthread_mutex_unlock! actually checks at run-time that the mutex is +locked on entrance, and that it was locked by the same thread that is +now calling !pthread_mutex_unlock!. If these conditions are not met, +an error code is returned and the mutex remains unchanged. ``Fast'' +mutexes perform no such checks, thus allowing a locked mutex to be +unlocked by a thread other than its owner. This is non-portable behavior +and must not be relied upon. !pthread_mutex_destroy! destroys a mutex object, freeing the resources it might hold. The mutex must be unlocked on entrance. In the |