From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 3/3] prctl.2: tfix
Date: Sun, 28 Feb 2016 01:32:41 +0100 [thread overview]
Message-ID: <1456619561-613-3-git-send-email-jwilk@jwilk.net> (raw)
In-Reply-To: <1456619561-613-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
man2/prctl.2 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man2/prctl.2 b/man2/prctl.2
index 5cea3bb..1417a15 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -311,9 +311,9 @@ in the location pointed to by
.TP
.BR PR_SET_KEEPCAPS " (since Linux 2.2.18)"
Set the state of the thread's "keep capabilities" flag,
-which determines whether the threads's permitted
-capability set is cleared when a change is made to the threads's user IDs
-such that the threads's real UID, effective UID, and saved set-user-ID
+which determines whether the thread's permitted
+capability set is cleared when a change is made to the thread's user IDs
+such that the thread's real UID, effective UID, and saved set-user-ID
all become nonzero when at least one of them previously had the value 0.
By default, the permitted capability set is cleared when such a change is made;
setting the "keep capabilities" flag prevents it from being cleared.
@@ -328,7 +328,7 @@ The "keep capabilities" value will be reset to 0 on subsequent calls to
.BR execve (2).
.TP
.BR PR_GET_KEEPCAPS " (since Linux 2.2.18)"
-Return (as the function result) the current state of the calling threads's
+Return (as the function result) the current state of the calling thread's
"keep capabilities" flag.
.TP
.BR PR_MCE_KILL " (since Linux 2.6.32)"
--
2.7.0
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-28 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 0:32 [PATCH 1/3] getaddrinfo.3: tfix Jakub Wilk
[not found] ` <1456619561-613-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-02-28 0:32 ` [PATCH 2/3] capabilities.7: tfix Jakub Wilk
[not found] ` <1456619561-613-2-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-02-28 13:40 ` Michael Kerrisk (man-pages)
2016-02-28 0:32 ` Jakub Wilk [this message]
2016-02-28 13:39 ` [PATCH 1/3] getaddrinfo.3: tfix Michael Kerrisk (man-pages)
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=1456619561-613-3-git-send-email-jwilk@jwilk.net \
--to=jwilk-txgolizoknreowh0uzbu5w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).