From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: <mtk.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>, Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Subject: [PATCH] capget.2: Correct info about EPERM error
Date: Thu, 12 Dec 2019 15:23:55 +0800 [thread overview]
Message-ID: <1576135435-907-1-git-send-email-xuyang2018.jy@cn.fujitsu.com> (raw)
I see kernel code security/commoncap.c cap_capset function, it only
verifies the new_Effective is a subset of the new_Permitted. It doesn't
verify whether the new_Inheritable is a subset of the new_Permitted.
I found it when I cleanup ltp capset02 test code.
Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
---
man2/capget.2 | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/man2/capget.2 b/man2/capget.2
index 94d38d877..6cad3d5d8 100644
--- a/man2/capget.2
+++ b/man2/capget.2
@@ -195,8 +195,7 @@ One of the arguments was invalid.
.TP
.B EPERM
An attempt was made to add a capability to the Permitted set, or to set
-a capability in the Effective or Inheritable sets that is not in the
-Permitted set.
+a capability in the Effective sets that is not in the Permitted set.
.TP
.B EPERM
The caller attempted to use
--
2.18.0
next reply other threads:[~2019-12-12 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 7:23 Yang Xu [this message]
2019-12-12 8:36 ` [PATCH] capget.2: Correct info about EPERM error 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=1576135435-907-1-git-send-email-xuyang2018.jy@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.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).