From: Chengguang Xu <cgxu519@gmail.com>
To: ebiederm@xmission.com, jannh@google.com, serge@hallyn.com,
christian@brauner.io, keescook@chromium.org
Cc: linux-kernel@vger.kernel.org, Chengguang Xu <cgxu519@gmail.com>
Subject: [PATCH] ns: modify function comment for projid
Date: Sun, 5 May 2019 21:38:00 +0800 [thread overview]
Message-ID: <1557063480-4469-1-git-send-email-cgxu519@gmail.com> (raw)
Some function comments about projid are described
as uid, so fix it.
Signed-off-by: Chengguang Xu <cgxu519@gmail.com>
---
kernel/user_namespace.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/user_namespace.c b/kernel/user_namespace.c
index 923414a246e9..6e917fc072d0 100644
--- a/kernel/user_namespace.c
+++ b/kernel/user_namespace.c
@@ -516,8 +516,8 @@ EXPORT_SYMBOL(from_kgid_munged);
* @ns: User namespace that the projid is in
* @projid: Project identifier
*
- * Maps a user-namespace uid pair into a kernel internal kuid,
- * and returns that kuid.
+ * Maps a user-namespace projid pair into a kernel internal kprojid,
+ * and returns that kprojid.
*
* When there is no mapping defined for the user-namespace projid
* pair INVALID_PROJID is returned. Callers are expected to test
@@ -526,7 +526,7 @@ EXPORT_SYMBOL(from_kgid_munged);
*/
kprojid_t make_kprojid(struct user_namespace *ns, projid_t projid)
{
- /* Map the uid to a global kernel uid */
+ /* Map the projid to a global kernel projid */
return KPROJIDT_INIT(map_id_down(&ns->projid_map, projid));
}
EXPORT_SYMBOL(make_kprojid);
@@ -545,7 +545,7 @@ EXPORT_SYMBOL(make_kprojid);
*/
projid_t from_kprojid(struct user_namespace *targ, kprojid_t kprojid)
{
- /* Map the uid from a global kernel uid */
+ /* Map the projid from a global kernel projid */
return map_id_up(&targ->projid_map, __kprojid_val(kprojid));
}
EXPORT_SYMBOL(from_kprojid);
--
2.17.2
reply other threads:[~2019-05-05 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1557063480-4469-1-git-send-email-cgxu519@gmail.com \
--to=cgxu519@gmail.com \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®