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

openat2.2: srcfix: eliminate redundant blank lines 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2020-03-30 08:51:21 +02:00
parent 2359744f97
commit 2d82152f53
1 changed files with 2 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man2/openat2.2
View File

@ -88,7 +88,7 @@ must be set to
to facilitate future extensions (see the "Extensibility" section of the
.B NOTES
for more detail on how extensions are handled.)
.\"
.SS The open_how structure
The following structure indicates how
.I pathname
@ -243,7 +243,6 @@ However, this may change in the future.
The caller should explicitly specify
.B RESOLVE_NO_MAGICLINKS
to ensure that magic links are not resolved.
.TP
.B RESOLVE_IN_ROOT
Treat
@ -286,13 +285,11 @@ unknown flags in
.IR resolve .
.RE
.RE
.SH RETURN VALUE
On success, a new file descriptor is returned.
On error, -1 is returned, and
.I errno
is set appropriately.
.SH ERRORS
The set of errors returned by
.BR openat2 ()
@ -339,14 +336,12 @@ call.
contains either
.BR RESOLVE_IN_ROOT " or " RESOLVE_BENEATH ,
and an escape from the root during path resolution was detected.
.TP
.B EXDEV
.I resolve
contains
.BR RESOLVE_NO_XDEV ,
and a path component attempted to cross a mount point.
.TP
.B ELOOP
.I resolve
@ -359,11 +354,9 @@ and one of the path components was a symbolic link (or magic link).
contains
.BR RESOLVE_NO_MAGICLINKS ,
and one of the path components was a magic link.
.SH VERSIONS
.BR openat2 ()
first appeared in Linux 5.6.
.SH CONFORMING TO
This system call is Linux-specific.
@ -371,11 +364,10 @@ The semantics of
.B RESOLVE_BENEATH
were modelled after FreeBSD's
.BR O_BENEATH .
.SH NOTES
Glibc does not provide a wrapper for this system call; call it using
.BR syscall (2).
.\"
.SS Extensibility
In order to allow for
.I struct open_how
@ -399,7 +391,6 @@ be the size of the structure according to userspace and
.I ksize
be the size of the structure which the kernel supports, then there are only
three cases to consider:
.RS
.IP * 3
If
@ -466,7 +457,6 @@ supports, they may conduct a binary search on
with a structure which has every byte non-zero (to find the largest value
which doesn't produce an error of
.BR E2BIG .)
.SH SEE ALSO
.BR openat (2),
.BR path_resolution (7),