From: Mike Rapoport <rppt@linux.ibm.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH] memfd_create.2: fix typos
Date: Wed, 30 Oct 2019 23:39:18 +0100 [thread overview]
Message-ID: <1572475158-14919-1-git-send-email-rppt@linux.ibm.com> (raw)
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
man2/memfd_create.2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
index 15b1362..9be8f3c 100644
--- a/man2/memfd_create.2
+++ b/man2/memfd_create.2
@@ -221,7 +221,7 @@ used with the file-sealing APIs provided by
.PP
The
.BR memfd_create ()
-system call also has uses without file sealing
+system call also have uses without file sealing
(which is why file-sealing is disabled, unless explicitly requested with the
.BR MFD_ALLOW_SEALING
flag).
@@ -254,7 +254,7 @@ signal.)
Dealing with untrusted peers imposes extra complexity on
code that employs shared memory.
Memory sealing enables that extra complexity to be eliminated,
-by allowing a process to operate secure in the knowledge that
+by allowing a process to operate securely in the knowledge that
its peer can't modify the shared memory in an undesired fashion.
.PP
An example of the usage of the sealing mechanism is as follows:
--
2.7.4
next reply other threads:[~2019-10-30 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 22:39 Mike Rapoport [this message]
2019-10-30 22:40 ` [PATCH] memfd_create.2: fix typos Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1572475158-14919-1-git-send-email-rppt@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).