diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2008-11-24 17:35:16 -0500 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2008-11-25 20:54:26 -0500 |
| commit | f5410853fbe2fa9214b88a8dbee93148f98408cb (patch) | |
| tree | 7d51fa4d005442e85a2aa6e0756cf51bf4dfda1b /man3 | |
| parent | 0ac743c540732981c3c5c659b3932c9e25f1dc45 (diff) | |
| download | man-pages-f5410853fbe2fa9214b88a8dbee93148f98408cb.tar.gz | |
pthread_setcancelstate.3: spfix
Diffstat (limited to 'man3')
| -rw-r--r-- | man3/pthread_setcancelstate.3 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man3/pthread_setcancelstate.3 b/man3/pthread_setcancelstate.3 index 85af0309ec..1c0de7e3e9 100644 --- a/man3/pthread_setcancelstate.3 +++ b/man3/pthread_setcancelstate.3 @@ -128,7 +128,7 @@ Since the thread could be canceled at time, it cannot safely reserve resources (e.g., allocating memory with .BR malloc (3)), acquire mutexes, semaphores, or locks, and so on. -Reserving resources is unafe because the application has no way of +Reserving resources is unsafe because the application has no way of knowing what the state of these resources is when the thread is canceled; that is, did cancellation occur before the resources were reserved, while they were reserved, or after they were released? |