From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 1/2] Teach clients to map numeric strings into valid uids and gids.
Date: Tue, 17 Aug 2010 15:38:44 -0400 [thread overview]
Message-ID: <1282073925-18707-2-git-send-email-steved@redhat.com> (raw)
In-Reply-To: <1282073925-18707-1-git-send-email-steved@redhat.com>
When a server can not map a uid or gid they can send
an numeric string (one that does not include the @domain)
of the given id. When this occurs the client will can use
that numeric representation iff that id exists on the client.
Signed-off-by: Steve Dickson <steved@redhat.com>
---
utils/idmapd/idmapd.c | 38 ++++++++++++++++++++++++++++++++++++++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git a/utils/idmapd/idmapd.c b/utils/idmapd/idmapd.c
index 9ecab66..d6799c9 100644
--- a/utils/idmapd/idmapd.c
+++ b/utils/idmapd/idmapd.c
@@ -826,6 +826,21 @@ idtonameres(struct idmap_msg *im)
im->im_status = IDMAP_STATUS_SUCCESS;
}
+static int
+alldigits(char *name)
+{
+ char *p = name;
+
+ if (name == NULL)
+ return 0;
+
+ while (*p != '\0') {
+ if (!isdigit(*p++))
+ return 0;
+ }
+ return 1;
+}
+
static void
nametoidres(struct idmap_msg *im)
{
@@ -843,6 +858,18 @@ nametoidres(struct idmap_msg *im)
ret = nfs4_name_to_uid(im->im_name, &uid);
im->im_id = (u_int32_t) uid;
if (ret) {
+ /*
+ * When a server sends numeric string that's
+ * lacking the @domain part, and the uid exists
+ * use the numeric string as the uid.
+ */
+ if (alldigits(im->im_name)) {
+ sscanf(im->im_name, "%u", &uid);
+ if (getpwuid(uid) != NULL) {
+ im->im_id = uid;
+ break;
+ }
+ }
im->im_status = IDMAP_STATUS_LOOKUPFAIL;
im->im_id = nobodyuid;
}
@@ -851,6 +878,17 @@ nametoidres(struct idmap_msg *im)
ret = nfs4_name_to_gid(im->im_name, &gid);
im->im_id = (u_int32_t) gid;
if (ret) {
+ /*
+ * Do the same type of mapping of a numeric string
+ * sent as the gid.
+ */
+ if (alldigits(im->im_name)) {
+ sscanf(im->im_name, "%u", &gid);
+ if (getgrgid(gid) != NULL) {
+ im->im_id = gid;
+ break;
+ }
+ }
im->im_status = IDMAP_STATUS_LOOKUPFAIL;
im->im_id = nobodygid;
}
--
1.7.1
next prev parent reply other threads:[~2010-08-17 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 19:38 [PATCH 0/2] Support for Numeric Representations of UIDs and GIDs Steve Dickson
2010-08-17 19:38 ` Steve Dickson [this message]
2010-08-17 20:27 ` [PATCH 1/2] Teach clients to map numeric strings into valid uids and gids Trond Myklebust
2010-08-17 21:35 ` Steve Dickson
2010-08-17 21:47 ` Trond Myklebust
2010-08-17 22:07 ` Steve Dickson
2010-08-17 22:13 ` Trond Myklebust
2010-08-17 22:25 ` Steve Dickson
2010-08-17 19:38 ` [PATCH 2/2] Add server support to use of numeric strings for uid " Steve Dickson
2010-08-17 20:28 ` Trond Myklebust
2010-08-17 19:51 ` [PATCH 0/2] Support for Numeric Representations of UIDs and GIDs Tom Haynes
2010-08-17 20:04 ` Steve Dickson
[not found] ` <4C6AEB43.5080508-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-08-17 20:30 ` Tom Haynes
2010-08-18 18:20 ` J. Bruce Fields
2010-08-18 19:09 ` Steve Dickson
2010-08-18 19:17 ` J. Bruce Fields
2010-08-18 19:23 ` Trond Myklebust
[not found] ` <1282159391.8540.90.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-08-18 19:33 ` Steve Dickson
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=1282073925-18707-2-git-send-email-steved@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.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).