Provide an unambiguous description of the potential hazard in calling
pthread_setspecific(3) from a key destructor. Reviewed by: jhb Approved by: jmallett (mentor) MFC after: 3 days
This commit is contained in:
parent
b7d130befc
commit
e5315a56df
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=283652
@ -67,7 +67,10 @@ is undefined.
|
|||||||
The
|
The
|
||||||
.Fn pthread_setspecific
|
.Fn pthread_setspecific
|
||||||
function may be called from a thread-specific data destructor function,
|
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
|
.Sh RETURN VALUES
|
||||||
If successful, the
|
If successful, the
|
||||||
.Fn pthread_setspecific
|
.Fn pthread_setspecific
|
||||||
|
Loading…
Reference in New Issue
Block a user