From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] libnfsidmap: id_as_chars() fails zero value ids.
Date: Wed, 30 Apr 2014 13:31:14 -0400 [thread overview]
Message-ID: <53613362.8050109@RedHat.com> (raw)
In-Reply-To: <20140430123013.4c4cc8ec@tlielax.poochiereds.net>
On 04/30/2014 12:30 PM, Jeff Layton wrote:
> On Wed, 30 Apr 2014 11:18:28 -0400
> Steve Dickson <steved@redhat.com> wrote:
>
>> Root has a zero value id which is valid and
>> should not be mapped to nfsnobody
>>
>> Signed-off-by: Steve Dickson <steved@redhat.com>
>> ---
>> libnfsidmap.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/libnfsidmap.c b/libnfsidmap.c
>> index 641d766..92bc493 100644
>> --- a/libnfsidmap.c
>> +++ b/libnfsidmap.c
>> @@ -99,8 +99,12 @@ static char * toupper_str(char *s)
>> static int id_as_chars(char *name, int *id)
>> {
>> long int value = strtol(name, NULL, 10);
>> - if (value == 0)
>> - return 0;
>> +
>> + if (value == 0) {
>> + /* zero value ids are valid */
>> + if (strcmp(name, "0") != 0)
>> + return 0;
>> + }
>> *id = (int)value;
>> return 1;
>> }
>
> Well spotted. I think though that instead of doing the strcmp, you
> should instead just use the endptr value in the strtol call to determine
> whether the string was completely converted. If it isn't, we can just
> return 0 here. If it is completely converted then you know that you got
> a legit "0" string.
>
Yeah that wold have been a good idea but I've already
committed and pushed this version... ;-)
I'm thinking it's six of one and a half a dozen of another
both version will do the same thing... but if it bothersome,
send me a patch....
steved.
prev parent reply other threads:[~2014-04-30 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 15:18 [PATCH] libnfsidmap: id_as_chars() fails zero value ids Steve Dickson
2014-04-30 16:30 ` Jeff Layton
2014-04-30 17:31 ` Steve Dickson [this message]
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=53613362.8050109@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@poochiereds.net \
--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).