Date: Thu, 4 Jun 2015 04:50:53 +0000 (UTC) From: Patrick Kelsey <pkelsey@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-10@freebsd.org Subject: svn commit: r283977 - stable/10/share/man/man3 Message-ID: <201506040450.t544orJN012582@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: pkelsey Date: Thu Jun 4 04:50:52 2015 New Revision: 283977 URL: https://svnweb.freebsd.org/changeset/base/283977 Log: MFC r283652: Provide an unambiguous description of the potential hazard in calling pthread_setspecific(3) from a key destructor. Modified: stable/10/share/man/man3/pthread_setspecific.3 Modified: stable/10/share/man/man3/pthread_setspecific.3 ============================================================================== --- stable/10/share/man/man3/pthread_setspecific.3 Thu Jun 4 02:50:13 2015 (r283976) +++ stable/10/share/man/man3/pthread_setspecific.3 Thu Jun 4 04:50:52 2015 (r283977) @@ -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?201506040450.t544orJN012582>