attributes.7: Fixes from Peng Haitao

Reviewed-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-10-28 14:12:05 +01:00
parent 61129eb810
commit 7236d18fbf
1 changed files with 6 additions and 6 deletions

View File

@ -679,7 +679,7 @@ environment with
or similar, without any guards to ensure or similar, without any guards to ensure
safety in the presence of concurrent modifications. safety in the presence of concurrent modifications.
We do not mark these functions as MT-Unsafe \" or AS-Unsafe, We do not mark these functions as MT-Unsafe, \" or AS-Unsafe,
however, however,
because functions that modify the environment are all marked with because functions that modify the environment are all marked with
.I const:env .I const:env
@ -718,9 +718,9 @@ GNU C Library
internal data structure without any guards to ensure internal data structure without any guards to ensure
safety in the presence of concurrent modifications. safety in the presence of concurrent modifications.
We do not mark these functions as MT-Unsafe \" or AS-Unsafe, We do not mark these functions as MT-Unsafe, \" or AS-Unsafe,
however, however,
because functions that modify the this data structure are all marked with because functions that modify this data structure are all marked with
.I const:sigintr .I const:sigintr
and regarded as unsafe. and regarded as unsafe.
Being unsafe, Being unsafe,
@ -799,8 +799,8 @@ change the current working directory during their execution,
which may cause relative pathnames to be resolved in unexpected ways in 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 cancellation handlers.
This is not enough of a reason to mark so-marked functions as MT-Unsafe This is not enough of a reason to mark so-marked functions as MT-Unsafe,
\" or AS-Unsafe, .\" or AS-Unsafe,
but when this behavior is optional (e.g., but when this behavior is optional (e.g.,
.BR nftw (3) .BR nftw (3)
with with
@ -867,7 +867,7 @@ global variables or even the underlying kernel evaluates evaluates to true.
.\" applies when the underlying kernel is the HURD, .\" applies when the underlying kernel is the HURD,
.\" or when it is neither Linux nor a BSD kernel, respectively. .\" or when it is neither Linux nor a BSD kernel, respectively.
For example, For example,
.I !ps .I /!ps
and and
.I /one_per_line .I /one_per_line
indicate the preceding marker only applies when argument indicate the preceding marker only applies when argument