Messages in this thread | | | Date | Fri, 20 Feb 2015 13:58:15 -0500 | From | Jeff Layton <> | Subject | Re: [RFC PATCH 5/8] KEYS: exec request-key within the requesting task's init namespace |
| |
On Fri, 20 Feb 2015 12:07:15 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes: > > > On Fri, Feb 20, 2015 at 05:33:25PM +0800, Ian Kent wrote: > > >> The case of nfsd state-recovery might be similar but you'll need to help > >> me out a bit with that too. > > > > Each network namespace can have its own virtual nfs server. Servers can > > be started and stopped independently per network namespace. We decide > > which server should handle an incoming rpc by looking at the network > > namespace associated with the socket that it arrived over. > > > > A server is started by the rpc.nfsd command writing a value into a magic > > file somewhere. > > nit. Unless I am completely turned around that file is on the nfsd > filesystem, that lives in fs/nfsd/nfs.c. >
Correct.
> So I bevelive this really is a case of figuring out what we want the > semantics to be for mount and propogating the information down from > mount to where we call the user mode helpers. >
Hmmm. I'm a little confused here. Are you saying that the namespace for nfsd's upcalls umh ought to be derived from the process that did the initial mount of /proc/fs/nfsd ?
-- Jeff Layton <jeff.layton@primarydata.com>
| |