Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756121AbZAGBow (ORCPT ); Tue, 6 Jan 2009 20:44:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752681AbZAGBoi (ORCPT ); Tue, 6 Jan 2009 20:44:38 -0500 Received: from mail.fieldses.org ([141.211.133.115]:42638 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757329AbZAGBoh (ORCPT ); Tue, 6 Jan 2009 20:44:37 -0500 Date: Tue, 6 Jan 2009 20:44:22 -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: <20090107014422.GA17913@fieldses.org> References: <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> <20090107002608.GK13785@fieldses.org> <1231288706.11487.15.camel@heimdal.trondhjem.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1231288706.11487.15.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 Content-Length: 1584 Lines: 38 On Tue, Jan 06, 2009 at 07:38:26PM -0500, Trond Myklebust wrote: > On Tue, 2009-01-06 at 19:26 -0500, J. Bruce Fields wrote: > > 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. > > Why? > > > 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. > > Again, why? Are you seriously proposing a plan to transport all NFS and > locking state directly from one kernel to another? If people seem to think they can do live process and container migration: http://ols.fedoraproject.org/OLS/Reprints-2008/mirkin-reprint.pdf then moving the NFS state strikes me as not the greatest of their troubles. I'm not volunteering! --b. -- 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/