Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755364AbbBTS6V (ORCPT ); Fri, 20 Feb 2015 13:58:21 -0500 Received: from mail-yh0-f42.google.com ([209.85.213.42]:44565 "EHLO mail-yh0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754848AbbBTS6S (ORCPT ); Fri, 20 Feb 2015 13:58:18 -0500 Date: Fri, 20 Feb 2015 13:58:15 -0500 From: Jeff Layton To: ebiederm@xmission.com (Eric W. Biederman) Cc: "J. Bruce Fields" , Ian Kent , David Howells , Kernel Mailing List , Oleg Nesterov , Trond Myklebust , Benjamin Coddington , Al Viro Subject: Re: [RFC PATCH 5/8] KEYS: exec request-key within the requesting task's init namespace Message-ID: <20150220135815.359730e6@tlielax.poochiereds.net> In-Reply-To: <877fvc319o.fsf@x220.int.ebiederm.org> References: <20150205023423.8382.69433.stgit@pluto.fritz.box> <20150205021553.8382.16297.stgit@pluto.fritz.box> <12365.1423149270@warthog.procyon.org.uk> <1423187245.3299.37.camel@pluto.fritz.box> <20150218170620.GI4148@fieldses.org> <20150218173132.GJ4148@fieldses.org> <20150218205908.GB12573@fieldses.org> <1424306341.2649.12.camel@pluto.fritz.box> <20150219013116.GA13131@fieldses.org> <1424424805.2632.24.camel@pluto.fritz.box> <20150220172558.GD18103@fieldses.org> <877fvc319o.fsf@x220.int.ebiederm.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1498 Lines: 40 On Fri, 20 Feb 2015 12:07:15 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote: > "J. Bruce Fields" 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/