linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Revert "mountd: handle allocation failures in auth_unix_ip upcall"
Date: Mon, 26 Nov 2012 17:38:49 -0500	[thread overview]
Message-ID: <A954A569-E030-4119-A349-6CB888979738@oracle.com> (raw)
In-Reply-To: <20121126221535.GB18186@fieldses.org>


On Nov 26, 2012, at 5:15 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Mon, Nov 26, 2012 at 05:05:22PM -0500, Chuck Lever wrote:
>> 
>> On Nov 26, 2012, at 5:03 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:
>> 
>>> From: "J. Bruce Fields" <bfields@redhat.com>
>>> 
>>> This reverts commit 485f7a21e1649797f29317b865cbb094c1f6a71d.  The
>>> failures handled there could be any sort of name resolution failure, not
>>> just an allocation, and failing to downcall (hence leaving the client
>>> hanging) is not the correct thing to do in those cases.
>> 
>> The problem is in the kernel, then: a downcall should be allowed to fail, IMO.
> 
> In this case, after a revert, a failure here will result in the downcall
> passing down a client named "DEFAULT".  Presumably that won't be
> permitted access to the export, so the client will end up getting an
> error.

"A failure here" can mean either malloc() returned NULL in client_resolve() or client_compose(), or . . . ?

> But I may not understand your objection.

The main problem is I don't understand your patch description.  :-)

I don't seem to have commit 485f7a21 in my nfs-utils git tree (it's helpful to include the short description for such a case).

What exactly is the problem with the current code?

client_resolve() can return a NULL in some cases.  Why is it OK to pass a NULL "ai" to client_compose() ?  Looks like that can result in a mountd segfault.  The kernel won't get any downcall reply in that case!  Is that what you are trying to fix?

WRT my original objection: In general I don't see how to make it impossible for mountd to fail.  Thus the kernel needs to be better about recovering when mountd suddenly disappears.

> 
> --b.
> 
>> 
>>> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
>>> ---
>>> utils/mountd/cache.c | 12 +++---------
>>> 1 file changed, 3 insertions(+), 9 deletions(-)
>>> 
>>> diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c
>>> index 8f14032..6710eca 100644
>>> --- a/utils/mountd/cache.c
>>> +++ b/utils/mountd/cache.c
>>> @@ -84,6 +84,7 @@ static void auth_unix_ip(FILE *f)
>>> 	char ipaddr[INET6_ADDRSTRLEN];
>>> 	char *client = NULL;
>>> 	struct addrinfo *tmp = NULL;
>>> +	struct addrinfo *ai = NULL;
>>> 	if (readline(fileno(f), &lbuf, &lbuflen) != 1)
>>> 		return;
>>> 
>>> @@ -106,16 +107,12 @@ static void auth_unix_ip(FILE *f)
>>> 
>>> 	/* addr is a valid, interesting address, find the domain name... */
>>> 	if (!use_ipaddr) {
>>> -		struct addrinfo *ai = NULL;
>>> -
>>> 		ai = client_resolve(tmp->ai_addr);
>>> -		if (ai == NULL)
>>> -			goto out;
>>> 		client = client_compose(ai);
>>> 		freeaddrinfo(ai);
>>> -		if (!client)
>>> -			goto out;
>>> 	}
>>> +	freeaddrinfo(tmp);
>>> +
>>> 	qword_print(f, "nfsd");
>>> 	qword_print(f, ipaddr);
>>> 	qword_printuint(f, time(0) + DEFAULT_TTL);
>>> @@ -127,9 +124,6 @@ static void auth_unix_ip(FILE *f)
>>> 	xlog(D_CALL, "auth_unix_ip: client %p '%s'", client, client?client: "DEFAULT");
>>> 
>>> 	free(client);
>>> -out:
>>> -	freeaddrinfo(tmp);
>>> -
>>> }
>>> 
>>> static void auth_unix_gid(FILE *f)
>>> -- 
>>> 1.7.11.7
>>> 
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> 
>> --
>> Chuck Lever
>> chuck[dot]lever[at]oracle[dot]com
>> 
>> 
>> 

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




  reply	other threads:[~2012-11-26 22:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 22:03 [PATCH] Revert "mountd: handle allocation failures in auth_unix_ip upcall" J. Bruce Fields
2012-11-26 22:05 ` Chuck Lever
2012-11-26 22:15   ` J. Bruce Fields
2012-11-26 22:38     ` Chuck Lever [this message]
2012-11-26 22:51       ` J. Bruce Fields
2012-11-26 23:10         ` Chuck Lever
2012-11-27 14:23         ` Steve Dickson
2012-11-27 21:31         ` J. Bruce Fields
2012-11-27 21:33           ` Chuck Lever
2012-11-28 14:39           ` 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=A954A569-E030-4119-A349-6CB888979738@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.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).