Date: Thu, 28 May 2015 16:18:42 +0000 (UTC) From: Patrick Kelsey <pkelsey@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r283652 - head/share/man/man3 Message-ID: <201505281618.t4SGIgme010937@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: pkelsey Date: Thu May 28 16:18:41 2015 New Revision: 283652 URL: https://svnweb.freebsd.org/changeset/base/283652 Log: 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 Modified: head/share/man/man3/pthread_setspecific.3 Modified: head/share/man/man3/pthread_setspecific.3 ============================================================================== --- head/share/man/man3/pthread_setspecific.3 Thu May 28 16:16:29 2015 (r283651) +++ head/share/man/man3/pthread_setspecific.3 Thu May 28 16:18:41 2015 (r283652) @@ -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201505281618.t4SGIgme010937>