Re: [PATCH] Adding the nfs4_secure_mounts bool

From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Adding the nfs4_secure_mounts bool
Date: Tue, 12 Nov 2013 11:24:40 -0500	[thread overview]
Message-ID: <52825648.5090907@RedHat.com> (raw)
In-Reply-To: <784A1C68-59DA-4248-AF91-BAF472CDD37E@oracle.com>

On 12/11/13 11:09, Chuck Lever wrote:
>> In the past, if admins want rpc.gssd in the mount path they had to configure it.
>> > Now we are silently adding, yet another, daemon to the mount path and if 
>> > rpc.gssd starts falling on its face, I think it will be difficult to debug,
>> > since the daemon is not expected to be there...
> Our only real choice here is to fix gssd.  Anything else is punting the problem down the road.
> 
No. The last there was a daemon was involved in all NFS client mounts 
(at least that I can remember) was when lockd was a user level daemon.
The main reason it was ported to the kernel was to get ride of the
bottle neck it caused... Now we adding similar bottle neck back??

Architecturally, put a daemon in the direct NFS mount path just does 
not make sense... IMHO...

steved.