Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754874AbZAFUVJ (ORCPT ); Tue, 6 Jan 2009 15:21:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751968AbZAFUUz (ORCPT ); Tue, 6 Jan 2009 15:20:55 -0500 Received: from mail.fieldses.org ([141.211.133.115]:45972 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751869AbZAFUUy (ORCPT ); Tue, 6 Jan 2009 15:20:54 -0500 Date: Tue, 6 Jan 2009 15:20:46 -0500 To: "Serge E. Hallyn" Cc: Matt Helsley , Linux Containers , linux-nfs@vger.kernel.org, Linux Kernel Mailing List , Trond Myklebust , Chuck Lever , "Eric W. Biederman" , Linux Containers , Cedric Le Goater Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Message-ID: <20090106202046.GF5901@fieldses.org> References: <20090106011314.534653345@us.ibm.com> <20090106011314.961946803@us.ibm.com> <20090106200229.GA17031@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090106200229.GA17031@us.ibm.com> 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: 3136 Lines: 80 On Tue, Jan 06, 2009 at 02:02:29PM -0600, Serge E. Hallyn wrote: > Quoting Matt Helsley (matthltc@us.ibm.com): > > We can often specify the UTS namespace to use when starting an RPC client. > > However sometimes no UTS namespace is available (specifically during system > > shutdown as the last NFS mount in a container is unmounted) so fall > > back to the initial UTS namespace. > > So what happens if we take this patch and do nothing else? > > The only potential problem situation will be rpc requests > made on behalf of a container in which the last task has > exited, right? So let's say a container did an nfs mount > and then exits, causing an nfs umount request. > > That umount request will now be sent with the wrong nodename. > Does that actually cause problems, will the server use the > nodename to try and determine the client sending the request? This is just the machine name in the auth_unix credential? The linux server ignores that completely (for the purpose of auth_unix authenication, it identifies clients only by source ip address). I suspect other servers also ignore it, but I don't know. --b. > > thanks, > -serge > > > Signed-off-by: Matt Helsley > > Cc: Cedric Le Goater > > Cc: Linux Kernel Mailing List > > Cc: linux-nfs@vger.kernel.org > > Cc: Trond Myklebust > > Cc: Chuck Lever > > Cc: Eric W. Biederman > > Cc: Linux Containers > > > > --- > > net/sunrpc/clnt.c | 7 +++++-- > > 1 file changed, 5 insertions(+), 2 deletions(-) > > > > Index: linux-2.6.28/net/sunrpc/clnt.c > > =================================================================== > > --- linux-2.6.28.orig/net/sunrpc/clnt.c > > +++ linux-2.6.28/net/sunrpc/clnt.c > > @@ -128,6 +128,7 @@ static struct rpc_clnt * rpc_new_client( > > struct rpc_version *version; > > struct rpc_clnt *clnt = NULL; > > struct rpc_auth *auth; > > + struct new_utsname *uts_ns = init_utsname(); > > int err; > > size_t len; > > > > @@ -213,10 +214,12 @@ static struct rpc_clnt * rpc_new_client( > > } > > > > /* save the nodename */ > > - clnt->cl_nodelen = strlen(init_utsname()->nodename); > > + if (current->nsproxy != NULL) > > + uts_ns = utsname(); > > + clnt->cl_nodelen = strlen(uts_ns->nodename); > > if (clnt->cl_nodelen > UNX_MAXNODENAME) > > clnt->cl_nodelen = UNX_MAXNODENAME; > > - memcpy(clnt->cl_nodename, init_utsname()->nodename, clnt->cl_nodelen); > > + memcpy(clnt->cl_nodename, uts_ns->nodename, clnt->cl_nodelen); > > rpc_register_client(clnt); > > return clnt; > > > > > > -- > > _______________________________________________ > > Containers mailing list > > Containers@lists.linux-foundation.org > > https://lists.linux-foundation.org/mailman/listinfo/containers -- 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/