From 3fcaeb806a4a3861ecc33ef0379e37dd23a50ca3 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 30 Mar 2020 10:22:48 +0200 Subject: [PATCH] openat2.2: ffix Signed-off-by: Michael Kerrisk --- man2/openat2.2 | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/man2/openat2.2 b/man2/openat2.2 index ee625e5e1..26aab3a00 100644 --- a/man2/openat2.2 +++ b/man2/openat2.2 @@ -31,8 +31,8 @@ openat2 \- open and possibly create a file (extended) .B #include .B #include .PP -.BI "int openat2(int " dirfd ", const char *" pathname ", \ -struct open_how *" how ", size_t " size "); +.BI "int openat2(int " dirfd ", const char *" pathname , +.BI " struct open_how *" how ", size_t " size "); .fi .PP .IR Note : @@ -385,14 +385,13 @@ 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 +.IP \(bu 2 If .IR ksize " equals " usize , then there is no version mismatch and .I how can be used verbatim. -.IP * +.IP \(bu If .IR ksize " is larger than " usize , then there are some extensions the kernel supports which the userspace program @@ -400,7 +399,7 @@ is unaware of. Because all extensions must have their zero values be a no-op, the kernel treats all of the extension fields not set by userspace to have zero values. This provides backwards-compatibility. -.IP * +.IP \(bu If .IR ksize " is smaller than " usize , then there are some extensions which the userspace program is aware of but the @@ -412,7 +411,6 @@ If any unsupported extension fields are non-zero, then \-1 is returned and is set to .BR E2BIG . This provides forwards-compatibility. -.RE .PP Therefore most userspace programs will not need to have any special handling of extensions. @@ -429,7 +427,8 @@ initializer: .PP .in +4n .EX -struct open_how how = { .flags = O_RDWR, .resolve = RESOLVE_IN_ROOT }; +struct open_how how = { .flags = O_RDWR, + .resolve = RESOLVE_IN_ROOT }; .EE .in .PP