diff options
| author | Samanta Navarro <ferivoz@riseup.net> | 2021-11-24 11:58:58 +0000 |
|---|---|---|
| committer | Alejandro Colomar <alx.manpages@gmail.com> | 2021-12-18 19:32:51 +0100 |
| commit | 1f08fc80e4573f8b6356296e511164477b935678 (patch) | |
| tree | ca414163a142e6675b64dc3a1a208b017ff48904 /man7 | |
| parent | 79c9fe57dd2164c1c58496034851fc499cc91958 (diff) | |
| download | man-pages-1f08fc80e4573f8b6356296e511164477b935678.tar.gz | |
pthread_cancel.3, pthread_cleanup_push_defer_np.3, pthread_setcancelstate.3, pthread_testcancel.3, pthreads.7: tfix
Changed cancellation to cancelation.
Signed-off-by: Samanta Navarro <ferivoz@riseup.net>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Diffstat (limited to 'man7')
| -rw-r--r-- | man7/aio.7 | 4 | ||||
| -rw-r--r-- | man7/attributes.7 | 42 | ||||
| -rw-r--r-- | man7/nptl.7 | 2 | ||||
| -rw-r--r-- | man7/pthreads.7 | 28 | ||||
| -rw-r--r-- | man7/signal-safety.7 | 6 |
5 files changed, 41 insertions, 41 deletions
diff --git a/man7/aio.7 b/man7/aio.7 index 72287be066..959c354254 100644 --- a/man7/aio.7 +++ b/man7/aio.7 @@ -209,7 +209,7 @@ the program retrieves their status using The .B SIGQUIT signal (generated by typing control-\e) causes the program to request -cancellation of each of the outstanding requests using +cancelation of each of the outstanding requests using .BR aio_cancel (3). .PP Here is an example of what we might see when running this program. @@ -371,7 +371,7 @@ main(int argc, char *argv[]) /* On receipt of SIGQUIT, attempt to cancel each of the outstanding I/O requests, and display status returned - from the cancellation requests. */ + from the cancelation requests. */ printf("got SIGQUIT; canceling I/O requests: \en"); diff --git a/man7/attributes.7 b/man7/attributes.7 index 580ebfe868..fdf91e1c0f 100644 --- a/man7/attributes.7 +++ b/man7/attributes.7 @@ -85,7 +85,7 @@ safe for inlining. .\" .I AC-Safe .\" .I AC-Safe .\" or Async-Cancel-Safe functions are safe to call when -.\" asynchronous cancellation is enabled. +.\" asynchronous cancelation is enabled. .\" AC in AC-Safe stands for Asynchronous Cancellation. .\" .\" The POSIX standard defines only three functions to be AC-Safe, namely @@ -99,10 +99,10 @@ safe for inlining. .\" This documentation is provided for use .\" by the GNU C Library developers. .\" -.\" Just like signal handlers, cancellation cleanup routines must configure +.\" Just like signal handlers, cancelation cleanup routines must configure .\" the floating point environment they require. .\" The routines cannot assume a floating point environment, -.\" particularly when asynchronous cancellation is enabled. +.\" particularly when asynchronous cancelation is enabled. .\" If the configuration of the floating point .\" environment cannot be performed atomically then it is also possible that .\" the environment encountered is internally inconsistent. @@ -174,7 +174,7 @@ Other keywords that appear in safety notes are defined in subsequent sections. .\" AS-Unsafe features in this section indicate the functions are never safe .\" to call when asynchronous signals are enabled. .\" AC-Unsafe features -.\" indicate they are never safe to call when asynchronous cancellation is +.\" indicate they are never safe to call when asynchronous cancelation is .\" .\" enabled. .\" There are no MT-Unsafe marks in this section. .\" .TP @@ -190,7 +190,7 @@ Other keywords that appear in safety notes are defined in subsequent sections. .\" .I lock .\" as an AC-Unsafe feature may, if canceled asynchronously, .\" fail to release a lock that would have been released if their execution -.\" had not been interrupted by asynchronous thread cancellation. +.\" had not been interrupted by asynchronous thread cancelation. .\" Once a lock is left taken, .\" attempts to take that lock will block indefinitely. .\" .TP @@ -319,7 +319,7 @@ Other keywords that appear in safety notes are defined in subsequent sections. .\" AS-Unsafe, because calling them in signal handlers may interfere with .\" timers set in the interrupted code, and AC-Unsafe, .\" because there is no safe way to guarantee an earlier timer -.\" will be reset in case of asynchronous cancellation. +.\" will be reset in case of asynchronous cancelation. .\" .\" .SS Conditionally safe features @@ -366,7 +366,7 @@ the function can then be safely called after other threads are started. .\" .I init .\" as an AS-Safety or AC-Unsafe feature should ensure .\" the initialization is performed -.\" before configuring signal handlers or enabling cancellation, +.\" before configuring signal handlers or enabling cancelation, .\" so that the AS-Safety and AC-Safety issues related with .\" .I libc_once .\" do not arise. @@ -565,16 +565,16 @@ blocking that signal before the call and resetting its handler afterwards is recommended. .\" .\" There is no safe way to guarantee the original signal handler is -.\" restored in case of asynchronous cancellation, +.\" restored in case of asynchronous cancelation, .\" therefore so-marked functions are also AC-Unsafe. .\" -.\" .\" fixme: at least deferred cancellation should get it right, and would +.\" .\" fixme: at least deferred cancelation should get it right, and would .\" .\" obviate the restoring bit below, and the qualifier above. .\" .\" Besides the measures recommended to work around the .\" MT-Safety and AS-Safety problem, -.\" in order to avert the cancellation problem, -.\" disabling asynchronous cancellation +.\" in order to avert the cancelation problem, +.\" disabling asynchronous cancelation .\" .I and .\" installing a cleanup handler to restore the signal to the desired state .\" and to release the mutex are recommended. @@ -616,13 +616,13 @@ even if referenced by different file descriptors. .\" restore terminal settings to their original state, .\" after temporarily changing them, but they may fail to do so if canceled. .\" -.\" .\" fixme: at least deferred cancellation should get it right, and would +.\" .\" fixme: at least deferred cancelation should get it right, and would .\" .\" obviate the restoring bit below, and the qualifier above. .\" .\" Besides the measures recommended to work around the .\" MT-Safety and AS-Safety problem, -.\" in order to avert the cancellation problem, -.\" disabling asynchronous cancellation +.\" in order to avert the cancelation problem, +.\" disabling asynchronous cancelation .\" .I and .\" installing a cleanup handler to .\" restore the terminal settings to the original state and to release the @@ -733,7 +733,7 @@ which makes the former safe. .\" Functions annotated with .\" .I fd .\" as an AC-Safety issue may leak file -.\" descriptors if asynchronous thread cancellation interrupts their +.\" descriptors if asynchronous thread cancelation interrupts their .\" execution. .\" .\" Functions that allocate or deallocate file descriptors will generally be @@ -755,7 +755,7 @@ which makes the former safe. .\" reallocated by another thread or signal handler. .\" .\" Such leaks could be internally avoided, with some performance penalty, -.\" by temporarily disabling asynchronous thread cancellation. +.\" by temporarily disabling asynchronous thread cancelation. .\" However, .\" since callers of allocation or deallocation functions would have to do .\" this themselves, to avoid the same sort of leak in their own layer, @@ -768,26 +768,26 @@ which makes the former safe. .\" However, cumulative effects of such leaks may pose a .\" problem for some programs. .\" If this is the case, -.\" suspending asynchronous cancellation for the duration of calls +.\" suspending asynchronous cancelation for the duration of calls .\" to such functions is recommended. .\" .TP .\" .I mem .\" Functions annotated with .\" .I mem .\" as an AC-Safety issue may leak -.\" memory if asynchronous thread cancellation interrupts their execution. +.\" memory if asynchronous thread cancelation interrupts their execution. .\" .\" The problem is similar to that of file descriptors: there is no atomic .\" interface to allocate memory and store its address in the argument to a .\" cleanup handler, .\" or to release it and remove its address from that argument, -.\" without at least temporarily disabling asynchronous cancellation, +.\" without at least temporarily disabling asynchronous cancelation, .\" which these functions do not do. .\" .\" This remark does not by itself cause a function to be regarded as .\" generally AC-Unsafe. .\" However, cumulative effects of such leaks may be -.\" severe enough for some programs that disabling asynchronous cancellation +.\" severe enough for some programs that disabling asynchronous cancelation .\" for the duration of calls to such functions may be required. .TP .I cwd @@ -796,7 +796,7 @@ Functions marked with as an MT-Safety issue may temporarily change the current working directory during their execution, which may cause relative pathnames to be resolved in unexpected ways in -other threads or within asynchronous signal or cancellation handlers. +other threads or within asynchronous signal or cancelation handlers. .IP This is not enough of a reason to mark so-marked functions as MT-Unsafe, .\" or AS-Unsafe, diff --git a/man7/nptl.7 b/man7/nptl.7 index 0133c0a104..ea179406db 100644 --- a/man7/nptl.7 +++ b/man7/nptl.7 @@ -34,7 +34,7 @@ Linux systems. .SS NPTL and signals NPTL makes internal use of the first two real-time signals (signal numbers 32 and 33). -One of these signals is used to support thread cancellation and POSIX timers +One of these signals is used to support thread cancelation and POSIX timers (see .BR timer_create (2)); the other is used as part of a mechanism that ensures all threads in diff --git a/man7/pthreads.7 b/man7/pthreads.7 index 6f4f6e763c..380aeb2175 100644 --- a/man7/pthreads.7 +++ b/man7/pthreads.7 @@ -257,17 +257,17 @@ pthread_setcanceltype() .in .SS Cancellation points POSIX.1 specifies that certain functions must, -and certain other functions may, be cancellation points. +and certain other functions may, be cancelation points. If a thread is cancelable, its cancelability type is deferred, -and a cancellation request is pending for the thread, +and a cancelation request is pending for the thread, then the thread is canceled when it calls a function -that is a cancellation point. +that is a cancelation point. .PP -The following functions are required to be cancellation points by +The following functions are required to be cancelation points by POSIX.1-2001 and/or POSIX.1-2008: .PP .\" FIXME -.\" Document the list of all functions that are cancellation points in glibc +.\" Document the list of all functions that are cancelation points in glibc .in +4n .EX accept() @@ -331,7 +331,7 @@ writev() .EE .in .PP -The following functions may be cancellation points according to +The following functions may be cancelation points according to POSIX.1-2001 and/or POSIX.1-2008: .PP .in +4n @@ -567,23 +567,23 @@ wscanf() .in .PP An implementation may also mark other functions -not specified in the standard as cancellation points. +not specified in the standard as cancelation points. In particular, an implementation is likely to mark -any nonstandard function that may block as a cancellation point. +any nonstandard function that may block as a cancelation point. (This includes most functions that can touch files.) .PP It should be noted that even if an application is not using -asynchronous cancellation, that calling a function from the above list +asynchronous cancelation, that calling a function from the above list from an asynchronous signal handler may cause the equivalent of -asynchronous cancellation. +asynchronous cancelation. The underlying user code may not expect -asynchronous cancellation and the state of the user data may become +asynchronous cancelation and the state of the user data may become inconsistent. Therefore signals should be used with caution when -entering a region of deferred cancellation. -.\" So, scanning "cancellation point" comments in the glibc 2.8 header +entering a region of deferred cancelation. +.\" So, scanning "cancelation point" comments in the glibc 2.8 header .\" files, it looks as though at least the following nonstandard -.\" functions are cancellation points: +.\" functions are cancelation points: .\" endnetgrent .\" endspent .\" epoll_pwait diff --git a/man7/signal-safety.7 b/man7/signal-safety.7 index 9e8cd3fea1..b0108c87e2 100644 --- a/man7/signal-safety.7 +++ b/man7/signal-safety.7 @@ -322,9 +322,9 @@ is likely to remove from the list of async-signal-safe functions. .\" .IP * 3 -Asynchronous signal handlers that call functions which are cancellation -points and nest over regions of deferred cancellation may trigger -cancellation whose behavior is as if asynchronous cancellation had +Asynchronous signal handlers that call functions which are cancelation +points and nest over regions of deferred cancelation may trigger +cancelation whose behavior is as if asynchronous cancelation had occurred and may cause application state to become inconsistent. .\" .SS errno |