From 84a2ce0f18b36ee00b6c5ac9ecc41e2a6129171e Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 16 Aug 2021 08:35:59 +0200 Subject: [PATCH] memfd_secret.2: Minor edits to Mike Rapoport's patch Signed-off-by: Michael Kerrisk --- man2/memfd_secret.2 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/man2/memfd_secret.2 b/man2/memfd_secret.2 index 9d976f31c..69d23b861 100644 --- a/man2/memfd_secret.2 +++ b/man2/memfd_secret.2 @@ -54,7 +54,7 @@ Following the call, the file size should be set using .BR ftruncate (2). .PP The memory areas backing the file created with -.BR memfd_create(2) +.BR memfd_secret (2) are visible only to the processes that have access to the file descriptor. The memory region is removed from the kernel page tables and only the page tables of the processes holding the file descriptor @@ -66,7 +66,7 @@ system calls.) The following values may be bitwise ORed in .I flags to control the behavior of -.BR memfd_secret (2): +.BR memfd_secret (): .TP .B FD_CLOEXEC Set the close-on-exec flag on the new file descriptor, @@ -103,7 +103,7 @@ The memory region is locked into memory in the same way as with .BR mlock (2), so that it will never be written into swap. However the implementation of -.BR memfd_secret (2) +.BR memfd_secret () will not try to populate the whole range during the .BR mmap (2) call that attaches the region into the process's address space; @@ -116,7 +116,7 @@ and cannot exceed .BR RLIMIT_MEMLOCK . .SH RETURN VALUE On success, -.BR memfd_secret (2) +.BR memfd_secret () returns a new file descriptor. On error, \-1 is returned and .I errno @@ -141,11 +141,11 @@ There was insufficient memory to create a new anonymous file. is not implemented on this architecture. .SH VERSIONS The -.BR memfd_secret (2) +.BR memfd_secret () system call first appeared in Linux 5.14. .SH CONFORMING TO The -.BR memfd_secret (2) +.BR memfd_secret () system call is Linux-specific. .SH SEE ALSO .BR fcntl (2),