Re: [PATCH 3/3] mountd: fix crossmnt options in v2/v3 case

[Chuck Lever <chuck.lever@oracle.com>]

On 03/08/2010 01:41 PM, J. Bruce Fields wrote:
> On Mon, Mar 08, 2010 at 01:30:23PM -0500, Chuck Lever wrote:
>> On 03/08/2010 01:21 PM, J. Bruce Fields wrote:
>>> Occasionally we seem to hear from a security-conscious administrator
>>> who's running v4-only and is irritated that they have to firewall off
>>> mountd instead of just being able to kill it entirely.  The latter might
>>> reassure them, I suppose.
>>
>> I think Jeff had the idea of having mountd simply not set up its RPC
>> listeners in that case.  That looks easy to do.
>
> Sure, makes sense.
>
> But we might decide we want separate processes for servicing MOUNT
> requests and export upcalls anyway.
>
> In which case, call one rpc.mountd, the other nfsd-cache-helper, don't
> bother running "rpc.mountd" in the v4-only case, and, yay, we never have
> to answer the "why do I still have to run rpc.mountd?" question again.

Heh.

Separating these facilities would make mountd's RPC service 
implementation more standard.  Right now, it has to select() over the 
RPC listeners _and_ the cache upcall fds.  That means it has it's own 
"svc_run()" function, and thus doesn't use the RPC library's.

But it might get complicated if we want to retain functionality in 
mountd for kernels that don't have the new export cache...

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