From: Trond Myklebust Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Date: Tue, 06 Jan 2009 18:15:34 -0500 Message-ID: <1231283734.8041.6.camel@heimdal.trondhjem.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> Mime-Version: 1.0 Content-Type: text/plain Cc: "Serge E. Hallyn" , Matt Helsley , Linux Containers , linux-nfs@vger.kernel.org, Linux Kernel Mailing List , "J. Bruce Fields" , Chuck Lever , Linux Containers , Cedric Le Goater To: "Eric W. Biederman" Return-path: Received: from mail-out1.uio.no ([129.240.10.57]:55195 "EHLO mail-out1.uio.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750924AbZAFXPp (ORCPT ); Tue, 6 Jan 2009 18:15:45 -0500 In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, 2009-01-06 at 15:04 -0800, Eric W. Biederman wrote: > That implies to me you want to capture the value at mount time, and to > pass it in to the rpc_call creation, and only at very specific well > defined points where we interact with user space should we examine > current->utsname(). At which point there should be no question > of current->utsname() is valid as the user space process is alive. Why pretend that the filesystem is owned by a particular namespace? It can, and will be shared among many containers... Trond