Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753813AbZAFXP4 (ORCPT ); Tue, 6 Jan 2009 18:15:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751355AbZAFXPq (ORCPT ); Tue, 6 Jan 2009 18:15:46 -0500 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 Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces From: Trond Myklebust To: "Eric W. Biederman" 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 In-Reply-To: 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> Content-Type: text/plain Date: Tue, 06 Jan 2009 18:15:34 -0500 Message-Id: <1231283734.8041.6.camel@heimdal.trondhjem.org> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 52956E9E0AEBE3D0FFF9EFC0BD4B856847DA7890 X-UiO-SPAM-Test: remote_host: 68.40.183.129 spam_score: -49 maxlevel 200 minaction 2 bait 0 mail/h: 1 total 328 max/h 9 blacklist 0 greylist 0 ratelimit 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 781 Lines: 17 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 -- 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/