From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Date: Tue, 6 Jan 2009 19:26:08 -0500 Message-ID: <20090107002608.GK13785@fieldses.org> References: <20090106011314.534653345@us.ibm.com> <20090106011314.961946803@us.ibm.com> <20090106200229.GA17031@us.ibm.com> <1231274682.20316.65.camel@heimdal.trondhjem.org> <20090106215831.GE18147@us.ibm.com> <1231283734.8041.6.camel@heimdal.trondhjem.org> <20090106233238.GD13785@fieldses.org> <1231284943.8041.8.camel@heimdal.trondhjem.org> <1231287607.11487.0.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1231287607.11487.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Trond Myklebust Cc: "Eric W. Biederman" , "Serge E. Hallyn" , Matt Helsley , Linux Containers , linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux Kernel Mailing List , Chuck Lever , Linux Containers , Cedric Le Goater List-Id: containers.vger.kernel.org On Tue, Jan 06, 2009 at 07:20:07PM -0500, Trond Myklebust wrote: > As for the NFSv4 clientid, I can't see how you would ever want to use > anything other than the init->utsname(), since the requirement is only > that the clientid string be unique and preserved across reboots. The > server isn't allowed to interpret the contents of the clientid string. > Ditto for the RPCSEC_GSS machine creds that are used to establish the > clientid. If people eventually expect to be able to, say, migrate a container to another host while using an nfs mount as their storage, then they'd need the name to be that of the container, not of the host. Obviously we'd also need to ensure the container got its own nfsv4 client state, etc., etc., and it sounds like we're far from that. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Date: Tue, 6 Jan 2009 19:26:08 -0500 Message-ID: <20090107002608.GK13785@fieldses.org> References: <20090106011314.534653345@us.ibm.com> <20090106011314.961946803@us.ibm.com> <20090106200229.GA17031@us.ibm.com> <1231274682.20316.65.camel@heimdal.trondhjem.org> <20090106215831.GE18147@us.ibm.com> <1231283734.8041.6.camel@heimdal.trondhjem.org> <20090106233238.GD13785@fieldses.org> <1231284943.8041.8.camel@heimdal.trondhjem.org> <1231287607.11487.0.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Eric W. Biederman" , "Serge E. Hallyn" , Matt Helsley , Linux Containers , linux-nfs@vger.kernel.org, Linux Kernel Mailing List , Chuck Lever , Linux Containers , Cedric Le Goater To: Trond Myklebust Return-path: Received: from mail.fieldses.org ([141.211.133.115]:32843 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbZAGA0R (ORCPT ); Tue, 6 Jan 2009 19:26:17 -0500 In-Reply-To: <1231287607.11487.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Jan 06, 2009 at 07:20:07PM -0500, Trond Myklebust wrote: > As for the NFSv4 clientid, I can't see how you would ever want to use > anything other than the init->utsname(), since the requirement is only > that the clientid string be unique and preserved across reboots. The > server isn't allowed to interpret the contents of the clientid string. > Ditto for the RPCSEC_GSS machine creds that are used to establish the > clientid. If people eventually expect to be able to, say, migrate a container to another host while using an nfs mount as their storage, then they'd need the name to be that of the container, not of the host. Obviously we'd also need to ensure the container got its own nfsv4 client state, etc., etc., and it sounds like we're far from that. --b. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756898AbZAGA01 (ORCPT ); Tue, 6 Jan 2009 19:26:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752268AbZAGA0R (ORCPT ); Tue, 6 Jan 2009 19:26:17 -0500 Received: from mail.fieldses.org ([141.211.133.115]:32843 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbZAGA0R (ORCPT ); Tue, 6 Jan 2009 19:26:17 -0500 Date: Tue, 6 Jan 2009 19:26:08 -0500 To: Trond Myklebust Cc: "Eric W. Biederman" , "Serge E. Hallyn" , Matt Helsley , Linux Containers , linux-nfs@vger.kernel.org, Linux Kernel Mailing List , Chuck Lever , Linux Containers , Cedric Le Goater Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Message-ID: <20090107002608.GK13785@fieldses.org> References: <20090106011314.534653345@us.ibm.com> <20090106011314.961946803@us.ibm.com> <20090106200229.GA17031@us.ibm.com> <1231274682.20316.65.camel@heimdal.trondhjem.org> <20090106215831.GE18147@us.ibm.com> <1231283734.8041.6.camel@heimdal.trondhjem.org> <20090106233238.GD13785@fieldses.org> <1231284943.8041.8.camel@heimdal.trondhjem.org> <1231287607.11487.0.camel@heimdal.trondhjem.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1231287607.11487.0.camel@heimdal.trondhjem.org> User-Agent: Mutt/1.5.18 (2008-05-17) From: "J. Bruce Fields" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 06, 2009 at 07:20:07PM -0500, Trond Myklebust wrote: > As for the NFSv4 clientid, I can't see how you would ever want to use > anything other than the init->utsname(), since the requirement is only > that the clientid string be unique and preserved across reboots. The > server isn't allowed to interpret the contents of the clientid string. > Ditto for the RPCSEC_GSS machine creds that are used to establish the > clientid. If people eventually expect to be able to, say, migrate a container to another host while using an nfs mount as their storage, then they'd need the name to be that of the container, not of the host. Obviously we'd also need to ensure the container got its own nfsv4 client state, etc., etc., and it sounds like we're far from that. --b.