summaryrefslogtreecommitdiffstats
path: root/lib/libthr/thread/thr_cancel.c
diff options
context:
space:
mode:
authormtm <mtm@FreeBSD.org>2003-06-29 21:21:52 +0000
committermtm <mtm@FreeBSD.org>2003-06-29 21:21:52 +0000
commita810bddc153bedad5167855ef52ee1f9bc9f57cc (patch)
treebe0db3a8ab1b26666404e965e5bd32a14afe8dd1 /lib/libthr/thread/thr_cancel.c
parent44509f207ffb90a4c042b0c0dc5a3e9d028286e1 (diff)
downloadFreeBSD-src-a810bddc153bedad5167855ef52ee1f9bc9f57cc.zip
FreeBSD-src-a810bddc153bedad5167855ef52ee1f9bc9f57cc.tar.gz
In a critical section, separate the aquisition of the thread lock
and the disabling of signals. What we are really interested in is keeping track of recursive disabling of signals. We should not be recursively acquiring thread locks. Any such situations should be reorganized to not require a recursive lock. Separating the two out also allows us to block signals independent of acquiring thread locks. This will be needed in libthr in the near future when we put the pieces together to protect libc functions that use pthread mutexes and low level locks.
Diffstat (limited to 'lib/libthr/thread/thr_cancel.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud