LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

chown.2, futex.2, membarrier.2, memfd_create.2, mount.2, msgop.2, open.2, open_by_handle_at.2, perf_event_open.2, readv.2, sched_setscheduler.2, syslog.2, basename.3: ffix 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-02-03 08:46:16 +01:00
parent e6a05bfff2
commit def04e1ccf
13 changed files with 2 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
man2/chown.2
View File

@ -203,7 +203,6 @@ This flag is Linux-specific; define
.B _GNU_SOURCE
.\" Before glibc 2.16, defining _ATFILE_SOURCE sufficed
to obtain its definition.
.TP
.B AT_SYMLINK_NOFOLLOW
If

3
man2/futex.2
View File

@ -312,7 +312,6 @@ The arguments
and
.I val3
are ignored.
.\" FIXME(Torvald) I think we should remove this. Or maybe adapt to a
.\" different example.
.\" For
@ -350,7 +349,6 @@ The arguments
and
.I val3
are ignored.
.\" FIXME(Torvald) I think we should remove this. Or maybe adapt to
.\" a different example.
.\" For
@ -835,7 +833,6 @@ then the
bit shall be set in the futex word's value; in other words, this value is:
FUTEX_WAITERS | TID
.IP
(Note that is invalid for a PI futex word to have no owner and
.BR FUTEX_WAITERS

10
man2/membarrier.2
View File

@ -29,7 +29,6 @@ membarrier \- issue memory barriers on a set of threads
.B #include <linux/membarrier.h>
.sp
.BI "int membarrier(int " cmd ", int " flags ");
.sp
.SH DESCRIPTION
The
.BR membarrier ()
@ -69,7 +68,6 @@ calls does not outweigh the performance gain on the fast side.
The
.I cmd
argument is one of the following:
.TP
.B MEMBARRIER_CMD_QUERY
Query the set of supported commands.
@ -93,7 +91,6 @@ All threads on the system are targeted by this command.
The
.I flags
argument is currently unused and must be specified as 0.
.PP
All memory accesses performed in program order from each targeted thread
are guaranteed to be ordered with respect to
@ -117,7 +114,6 @@ The pair ordering is detailed as (O: ordered, X: not ordered):
barrier() X X O
smp_mb() X O O
membarrier() O O O
.SH RETURN VALUE
On success, the
.B MEMBARRIER_CMD_QUERY
@ -138,7 +134,6 @@ Therefore, with
.I flags
set to 0, error handling is required only for the first call to
.BR membarrier ().
.SH ERRORS
.TP
.B EINVAL
@ -151,7 +146,6 @@ is non-zero.
The
.BR membarrier ()
system call is not implemented by this kernel.
.SH VERSIONS
The
.BR membarrier ()
@ -160,9 +154,7 @@ system call was added in Linux 4.3.
.SH CONFORMING TO
.BR membarrier ()
is Linux-specific.
.SH NOTES
A memory barrier instruction is part of the instruction set of
architectures with weakly-ordered memory models.
It orders memory
@ -179,9 +171,7 @@ Examples where
.BR membarrier ()
can be useful include implementations
of Read-Copy-Update libraries and garbage collectors.
.SH EXAMPLE
Assuming a multithreaded application where "fast_path()" is executed
very frequently, and where "slow_path()" is executed infrequently, the
following code (x86) can be transformed using

1
man2/memfd_create.2
View File

@ -215,7 +215,6 @@ by allowing a process to operate secure in the knowledge that
its peer can't modify the shared memory in an undesired fashion.
An example of the usage of the sealing mechanism is as follows:
.IP 1. 3
The first process creates a
.I tmpfs

2
man2/mount.2
View File

@ -91,9 +91,7 @@ in the low order 16 bits:
.\" MS_SHARED
.\" Mount points that are marked SHARED propagate mount events
.\" to one another after being cloned.
.\" mount --make-rshared ==> MS_SHARED | MS_REC
.\" MS_SLAVE
.\" A previously shared mount point can be marked SLAVE, meaning
.\" it receives propagated events, but does not propagate events.

1
man2/msgop.2
View File

@ -589,7 +589,6 @@ sent: a message at Wed Mar 4 16:25:45 2015
.RB "$" " ./a.out \-r"
message received: a message at Wed Mar 4 16:25:45 2015
.fi
.in
.SS Program source

2
man2/open.2
View File

@ -710,7 +710,6 @@ in this case is different from the meaning of
.B O_EXCL
otherwise.)
There are two main use cases for
.\" Inspired by http://lwn.net/Articles/559147/
.BR O_TMPFILE :
@ -1099,7 +1098,6 @@ but does not necessarily have the intention to read or write.
This is typically used to open devices in order to get a file descriptor
for use with
.BR ioctl (2).
.LP
The (undefined) effect of
.B O_RDONLY | O_TRUNC

1
man2/open_by_handle_at.2
View File

@ -237,7 +237,6 @@ flag, and the symbolic link is not dereferenced; the
.B O_NOFOLLOW
flag, if specified, is ignored.
The caller must have the
.B CAP_DAC_READ_SEARCH
capability to invoke

9
man2/perf_event_open.2
View File

@ -1226,11 +1226,9 @@ Branch target is in hypervisor.
.TP
.B PERF_SAMPLE_BRANCH_PLM_ALL
A convenience value that is the three preceding values ORed together.
.P
In addition to the privilege value, at least one or more of the
following bits must be set.
.TP
.B PERF_SAMPLE_BRANCH_ANY
Any branch type.
@ -1265,7 +1263,6 @@ Branch is part of a hardware-generated call stack.
This requires hardware support, currently only found
on Intel x86 Haswell or newer.
.RE
.TP
.IR "sample_regs_user" " (since Linux 3.7)"
.\" commit 4018994f3d8785275ef0e7391b75c3462c029e56
@ -1492,7 +1489,6 @@ and you should use the
and
.I cap_user_rdpmc
fields instead.
.TP
.IR cap_bit0_is_deprecated " (since Linux 3.12)"
.\" commit fa7315871046b9a4c48627905691dbde57e51033
@ -1509,7 +1505,6 @@ and
.I cap_usr_rdpmc
map to the same bit and thus both features should
be used with caution.
.TP
.IR cap_user_rdpmc " (since Linux 3.12)"
.\" commit fa7315871046b9a4c48627905691dbde57e51033
@ -1816,7 +1811,6 @@ The values in the corresponding record (that follows the header)
depend on the
.I type
selected as shown.
.RS
.TP 4
.B PERF_RECORD_MMAP
@ -2131,7 +2125,6 @@ The branch was in a transactional memory transaction.
.IR abort " (since Linux 3.11)"
.\" commit 135c5612c460f89657c4698fe2ea753f6f667963
The branch was in an aborted transactional memory transaction.
.P
The entries are from most to least recent, so the first entry
has the most recent branch.
@ -2147,7 +2140,6 @@ The type of branches recorded is specified by the
.I branch_sample_type
field.
.RE
.TP
.IR abi ", " regs[weight(mask)]
If
@ -2693,7 +2685,6 @@ Prior to Linux 2.6.36
.\" commit ad0cf3478de8677f720ee06393b3147819568d6a
this ioctl always failed due to a bug
in the kernel.
.TP
.B PERF_EVENT_IOC_SET_OUTPUT
This tells the kernel to report event notifications to the specified

4
man2/readv.2
View File

@ -246,8 +246,8 @@ or at run time via the return value from
.IR sysconf(_SC_IOV_MAX) .
On modern Linux systems, the limit is 1024.
Back in Linux 2.0 days, this limit was 16.
\"
\"
.\"
.\"
.SS C library/kernel differences
The raw
.BR preadv ()

1
man2/sched_setscheduler.2
View File

@ -36,7 +36,6 @@ set and get scheduling policy/parameters
.BI " const struct sched_param *" param );
.sp
.BI "int sched_getscheduler(pid_t " pid );
.sp
.fi
.SH DESCRIPTION
The

1
man2/syslog.2
View File

@ -298,7 +298,6 @@ If the log level is not explicitly specified as part of the message,
it defaults to
.IR default_message_loglevel .
The conventional meaning of the log level is as follows:
.TS
lB lB lB
lB c l.

1
man3/basename.3
View File

@ -106,7 +106,6 @@ shows the strings returned by
and
.BR basename ()
for different paths:
.sp
.TS
lb lb lb
l l l l.