Vince Weaver | 20 May 2013 19:11
Picon

[patch] small flags clarficiation in perf_event_open()


While using the perf_event_open() manpage to enhance the trinity fuzzer
I noticed the statement about the "flags" argument was misleading.

Signed-off-by: Vince Weaver <vincent.weaver@...>

diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index f3850f0..14fb854 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
 <at>  <at>  -148,7 +148,9  <at>  <at>  instructions.
 .P
 The
 .I flags
-argument takes one of the following values:
+argument takes a 
+.RI bitwise- or 'd
+combination of zero or more of the following values:
 .TP
 .BR PERF_FLAG_FD_NO_GROUP
 .\" FIXME The following sentence is unclear
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Peng Haitao | 20 May 2013 07:42
Favicon

[PATCH] stdio_ext.3: ATTRIBUTES: Note functions that are not thread-safe

The functions __fbufsize(), __fpending(), __fpurge() and
__fsetlocking() are not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/stdio_ext.3 | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/man3/stdio_ext.3 b/man3/stdio_ext.3
index fb5767a..d2578fe 100644
--- a/man3/stdio_ext.3
+++ b/man3/stdio_ext.3
 <at>  <at>  -129,6 +129,25  <at>  <at>  output to a terminal is forced out, say before reading keyboard input.)
 The
 .BR __fpurge ()
 function discards the contents of the stream's buffer.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR __fbufsize (),
+.BR __fpending (),
+.BR __fpurge ()
+and
+.BR __fsetlocking ()
+functions do not lock the stream, so they are not thread-safe.
+.LP
+The
+.BR __flbf (),
+.BR __freadable (),
+.BR __freading (),
(Continue reading)

Peng Haitao | 20 May 2013 07:36
Favicon

[PATCH] re_comp.3: ATTRIBUTES: Note functions that are not thread-safe

The functions re_comp() and re_exec() are not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/re_comp.3 | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/man3/re_comp.3 b/man3/re_comp.3
index b1c3295..ca4ef64 100644
--- a/man3/re_comp.3
+++ b/man3/re_comp.3
 <at>  <at>  -63,6 +63,13  <at>  <at>  otherwise it returns a pointer to an appropriate error message.

 .BR re_exec ()
 returns 1 for a successful match, zero for failure.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR re_comp ()
+and
+.BR re_exec ()
+functions are not thread-safe.
 .SH CONFORMING TO
 4.3BSD.
 .SH NOTES
--

-- 
1.8.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
(Continue reading)

Peng Haitao | 20 May 2013 07:33
Favicon

[PATCH] drand48.3: ATTRIBUTES: Note functions that are not thread-safe

The functions drand48(), erand48(), lrand48(), nrand48(),
mrand48(), jrand48(), srand48(), seed48() and lcong48() are
not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/drand48.3 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/man3/drand48.3 b/man3/drand48.3
index 3dad8fc..d65ae3d 100644
--- a/man3/drand48.3
+++ b/man3/drand48.3
 <at>  <at>  -201,6 +201,21  <at>  <at>  has been called, a subsequent call to either
 or
 .BR seed48 ()
 will restore the standard values of \fIa\fP and \fIc\fP.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR drand48 (),
+.BR erand48 (),
+.BR lrand48 (),
+.BR nrand48 (),
+.BR mrand48 (),
+.BR jrand48 (),
+.BR srand48 (),
+.BR seed48 (),
+and
+.BR lcong48 ()
(Continue reading)

Peng Haitao | 20 May 2013 07:12
Favicon

[PATCH] a64l.3: ATTRIBUTES: Note function that is not thread-safe

The function l64a() is not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/a64l.3 | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/man3/a64l.3 b/man3/a64l.3
index 1f14b68..762ec79 100644
--- a/man3/a64l.3
+++ b/man3/a64l.3
 <at>  <at>  -59,6 +59,15  <at>  <at>  a-z	represent 38-63
 .fi
 .RE
 So 123 = 59*64^0 + 1*64^1 = "v/".
+.SH ATTRIBUTES
+.SS Multithreading(see pthreads(7))
+The
+.BR l64a ()
+function is not thread-safe.
+.LP
+The
+.BR a64l ()
+function is thread-safe.
 .SH CONFORMING TO
 POSIX.1-2001.
 .SH NOTES
--

-- 
1.8.1.4

(Continue reading)

Simon Paillard | 19 May 2013 16:38
Picon
Favicon

[PATCH] resolv.conf.5: explain how to set empty domain

See http://bugs.debian.org/463575
---
 man5/resolv.conf.5 |    1 +
 1 file changed, 1 insertion(+)

diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5
index 716b345..9f2f3f9 100644
--- a/man5/resolv.conf.5
+++ b/man5/resolv.conf.5
 <at>  <at>  -63,6 +63,7  <at>  <at>  until a maximum number of retries are made.)
 \fBdomain\fP Local domain name.
 Most queries for names within this domain can use short names
 relative to the local domain.
+If set to \(aq.\(aq, the root domain is considered.
 If no \fBdomain\fP entry is present, the domain is determined
 from the local hostname returned by
 .BR gethostname (2);
--

-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Michael Kerrisk | 18 May 2013 19:44
Picon

Re: Hyper linking SEE ALSO references

On 05/16/13 15:14, Jon Grant wrote:
> Hello Michael
> 
> Could I ask if there could be hyper links between the SEE ALSO links please?
> 
> http://man7.org/linux/man-pages/man3/aio_return.3.html
> 
> 
> This page has references to other pages:
> 
> SEE ALSO         top
> 
>        aio_cancel(3), aio_error(3), aio_fsync(3), aio_read(3),
>        aio_suspend(3), aio_write(3), lio_listio(3), aio(7)
> 
> 
> -- Could these be hyper linked? e.g. "aio_cancel(3)" would point to:
> http://man7.org/linux/man-pages/man3/aio_cancel.3.html
> 
> 
> With best regards, Jon

Thanks for the heads up, Jon. These *should* be linked, but a recent change 
in my scripts broke things. The scripts and site are fixed now. 

Cheers,

Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
(Continue reading)

Simon Paillard | 18 May 2013 00:58
Picon
Favicon

[PATCH] ip.7: IP_MULTICAST_IF setsockopt recognizes struct mreq (compatibility)

Kernel added compatibility only recently in
3a084ddb4bf299a6e898a9a07c89f3917f0713f7
See: http://bugs.debian.org/607979
---
 man7/ip.7 |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/man7/ip.7 b/man7/ip.7
index d5036ea..39715a3 100644
--- a/man7/ip.7
+++ b/man7/ip.7
 <at>  <at>  -542,6 +542,9  <at>  <at>  Argument is an
 .I ip_mreqn
 or
 .I ip_mreq
+.\" net: IP_MULTICAST_IF setsockopt now recognizes struct mreq
+.\" Commit: 3a084ddb4bf299a6e898a9a07c89f3917f0713f7
+(since Linux 3.5)
 structure similar to
 .BR IP_ADD_MEMBERSHIP .
 .IP
--

-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Continue reading)

Марк Коренберг | 15 May 2013 12:05
Picon
Gravatar

man 2 prctl

Description of PR_SET_NAME and PR_GET_NAME commands for prctl()
incorrectly says that this calls affect process. Really, these calls
affect "threads" (in other words, TID instead of PID). Therefore each
thread (i.e. TID) may have its own name.

--
Segmentation fault
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Peng Haitao | 15 May 2013 04:43
Favicon

[PATCH] qecvt.3: ATTRIBUTES: Note functions that are not thread-safe

The functions qecvt() and qfcvt() are not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/qecvt.3 | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/man3/qecvt.3 b/man3/qecvt.3
index 9cfa68d..07cbe59 100644
--- a/man3/qecvt.3
+++ b/man3/qecvt.3
 <at>  <at>  -69,6 +69,17  <at>  <at>  See
 .BR ecvt (3)
 and
 .BR gcvt (3).
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The functions
+.BR qecvt ()
+and
+.BR qfcvt ()
+are not thread-safe.
+.LP
+The function
+.BR qgcvt ()
+is thread-safe.
 .SH CONFORMING TO
 SVr4.
 Not seen in most common UNIX implementations,
--

-- 
(Continue reading)

Peng Haitao | 15 May 2013 04:28
Favicon

[PATCH] hsearch.3: ATTRIBUTES: Note functions that are not thread-safe

The functions hsearch(), hcreate() and hdestroy() are not thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/hsearch.3 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/man3/hsearch.3 b/man3/hsearch.3
index e66c840..3d6ae2e 100644
--- a/man3/hsearch.3
+++ b/man3/hsearch.3
 <at>  <at>  -223,6 +223,21  <at>  <at>  was not found in the table.
 POSIX.1-2001 specifies only the
 .B ENOMEM
 error.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The functions
+.BR hcreate (),
+.BR hsearch (),
+and
+.BR hdestroy ()
+use a global space for storing the table, so they are not thread-safe.
+.LP
+The functions
+.BR hcreate_r (),
+.BR hsearch_r (),
+and
+.BR hdestroy_r ()
+are thread-safe.
(Continue reading)


Gmane