diff options
| author | pkelsey <pkelsey@FreeBSD.org> | 2015-06-04 04:50:52 +0000 |
|---|---|---|
| committer | pkelsey <pkelsey@FreeBSD.org> | 2015-06-04 04:50:52 +0000 |
| commit | 82415e4370d95e7ae43e397fa8b6e4186bcdb505 (patch) | |
| tree | eea8d7e2fb487bf3a7c9bd227a1d82d26e2cbe6f /share/man/man3 | |
| parent | ada95a851cef316c8faef368af20b0c37cca78da (diff) | |
| download | FreeBSD-src-82415e4370d95e7ae43e397fa8b6e4186bcdb505.zip FreeBSD-src-82415e4370d95e7ae43e397fa8b6e4186bcdb505.tar.gz | |
MFC r283652:
Provide an unambiguous description of the potential hazard in calling
pthread_setspecific(3) from a key destructor.
Diffstat (limited to 'share/man/man3')
| -rw-r--r-- | share/man/man3/pthread_setspecific.3 | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/share/man/man3/pthread_setspecific.3 b/share/man/man3/pthread_setspecific.3 index 1ea3002..3153c99 100644 --- a/share/man/man3/pthread_setspecific.3 +++ b/share/man/man3/pthread_setspecific.3 @@ -67,7 +67,10 @@ is undefined. The .Fn pthread_setspecific function may be called from a thread-specific data destructor function, -however this may result in lost storage or infinite loops. +however this may result in lost storage or infinite loops if doing so +causes non-NULL key values to remain after +.Bq PTHREAD_DESTRUCTOR_ITERATIONS +iterations of destructor calls have been made. .Sh RETURN VALUES If successful, the .Fn pthread_setspecific |
