diff options
author | Carlos O'Donell <carlos@redhat.com> | 2019-10-04 15:58:08 -0400 |
---|---|---|
committer | Carlos O'Donell <carlos@redhat.com> | 2019-10-18 15:55:33 -0400 |
commit | 676b2f2050a354b7e1bdf4fec9406c9ed00b44f5 (patch) | |
tree | cfead1bd6afbb7cc4184d0a9aad73b043ad78425 | |
parent | 95c1056962a3f2297c94ce47f0eaf0c5b6563231 (diff) | |
download | glibc-676b2f2050a354b7e1bdf4fec9406c9ed00b44f5.zip glibc-676b2f2050a354b7e1bdf4fec9406c9ed00b44f5.tar.gz glibc-676b2f2050a354b7e1bdf4fec9406c9ed00b44f5.tar.bz2 |
nptl: Document AS-safe functions in cancellation.c.
Document in comments that __pthread_enable_asynccancel and
__pthread_disable_asynccancel must be AS-safe in general with
the exception of the act of cancellation.
-rw-r--r-- | nptl/cancellation.c | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/nptl/cancellation.c b/nptl/cancellation.c index 7712845..23d7b2b 100644 --- a/nptl/cancellation.c +++ b/nptl/cancellation.c @@ -24,7 +24,9 @@ /* The next two functions are similar to pthread_setcanceltype() but more specialized for the use in the cancelable functions like write(). - They do not need to check parameters etc. */ + They do not need to check parameters etc. These functions must be + AS-safe, with the exception of the actual cancellation, because they + are called by wrappers around AS-safe functions like write().*/ int attribute_hidden __pthread_enable_asynccancel (void) @@ -59,7 +61,8 @@ __pthread_enable_asynccancel (void) return oldval; } - +/* See the comment for __pthread_enable_asynccancel regarding + the AS-safety of this function. */ void attribute_hidden __pthread_disable_asynccancel (int oldtype) |