[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877fvc319o.fsf@x220.int.ebiederm.org>
Date: Fri, 20 Feb 2015 12:07:15 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: Ian Kent <ikent@...hat.com>, David Howells <dhowells@...hat.com>,
Kernel Mailing List <linux-kernel@...r.kernel.org>,
Oleg Nesterov <onestero@...hat.com>,
Trond Myklebust <trond.myklebust@...marydata.com>,
Benjamin Coddington <bcodding@...hat.com>,
Al Viro <viro@...IV.linux.org.uk>,
Jeff Layton <jeff.layton@...marydata.com>
Subject: Re: [RFC PATCH 5/8] KEYS: exec request-key within the requesting task's init namespace
"J. Bruce Fields" <bfields@...ldses.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.
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.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists