All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>, Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Adding the nfs4_use_min_auth module parameter
Date: Thu, 07 Nov 2013 16:40:18 -0500	[thread overview]
Message-ID: <527C08C2.9050807@RedHat.com> (raw)
In-Reply-To: <20131107160115.0f2bd8a8@tlielax.poochiereds.net>



On 07/11/13 16:01, Jeff Layton wrote:
> On Thu, 7 Nov 2013 11:25:19 -0800
> Chuck Lever <chuck.lever@oracle.com> wrote:
> 
>> Hi Steve-
>>
>> On Nov 7, 2013, at 11:09 AM, Steve Dickson <steved@redhat.com> wrote:
>>
>>> This new module parameter makes the v4 client
>>> use the minimal authentication flavor (AUTH_UNIX)
>>> when establishing NFSV4 state and doing the
>>> pseudoroot lookup
>>
>> The patch description doesn't say, but is this change to work around the 15 second GSSD upcall timeout? Have we completely given up on fixing the upcall?
>>
> 
> That would be my preferred solution too. The whole problem is that this
> upcall takes too damned long to time out.
> 
> But...how can it be fixed?
> 
> Due to the way that rpc_pipefs interface works, there's no way that I
> can see to make that fail immediately if no one is listening on the
> pipe. You could reduce the timeout I guess but that's sort of a
> half-assed solution.
> 
> IMO, we're long past due for a new upcall that uses a different design
> altogether. Maybe something based on call_usermodehelper that doesn't
> require a running daemon?
Bingo! I think it would be huge for all these upcalls to work like the idmapping
does on the client (aka via call_usermodehelper)... but which the likes
of Kerberos it may not be possible... 

steved.

> 

  reply	other threads:[~2013-11-07 21:39 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 19:09 [PATCH] Adding the nfs4_use_min_auth module parameter Steve Dickson
2013-11-07 19:25 ` Chuck Lever
2013-11-07 21:01   ` Jeff Layton
2013-11-07 21:40     ` Steve Dickson [this message]
2013-11-07 22:04       ` Jeff Layton
2013-11-07 21:35   ` Steve Dickson
2013-11-07 23:05     ` Chuck Lever
2013-11-08 12:41       ` Steve Dickson
2013-11-08 13:22         ` Jeff Layton
2013-11-08 15:00           ` Steve Dickson
2013-11-08 15:12             ` Jeff Layton
2013-11-08 16:10               ` Steve Dickson
2013-11-08 16:17                 ` J. Bruce Fields
2013-11-08 16:19                   ` Steve Dickson
2013-11-08 16:22                     ` J. Bruce Fields
2013-11-08 16:28                       ` Steve Dickson
2013-11-08 16:39                         ` J. Bruce Fields
2013-11-08 16:45                           ` Steve Dickson
2013-11-08 18:12                           ` Chuck Lever
2013-11-08 18:09                   ` Chuck Lever
2013-11-08 20:14                     ` J. Bruce Fields
2013-11-08 20:32                   ` Steve Dickson
2013-11-09  2:04               ` NeilBrown
2013-11-08 16:27             ` Weston Andros Adamson
2013-11-08 16:38               ` Steve Dickson
2013-11-08 15:04           ` J. Bruce Fields
2013-11-08 15:54             ` Chuck Lever
2013-11-08 16:14               ` J. Bruce Fields
2013-11-08 17:58                 ` Chuck Lever
2013-11-08 18:46                   ` Chuck Lever
2013-11-08 21:09                     ` J. Bruce Fields
2013-11-08 16:17               ` Steve Dickson
2013-11-08 15:46         ` Chuck Lever
2013-11-08 21:25           ` Steve Dickson
2013-11-07 19:26 ` Myklebust, Trond
2013-11-07 21:25   ` Steve Dickson
2013-11-07 21:39     ` Myklebust, Trond
2013-11-07 21:57       ` Steve Dickson
2013-11-07 22:29         ` Myklebust, Trond
2013-11-08 12:21           ` Steve Dickson
2013-11-08 14:30             ` Myklebust, Trond
2013-11-08 15:08               ` Steve Dickson
2013-11-08 15:16                 ` Myklebust, Trond
2013-11-08 16:31                   ` 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=527C08C2.9050807@RedHat.com \
    --to=steved@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.