Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757434AbZAGAVn (ORCPT ); Tue, 6 Jan 2009 19:21:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754463AbZAGAUd (ORCPT ); Tue, 6 Jan 2009 19:20:33 -0500 Received: from mail.fieldses.org ([141.211.133.115]:38249 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754002AbZAGAUb (ORCPT ); Tue, 6 Jan 2009 19:20:31 -0500 Date: Tue, 6 Jan 2009 19:20:24 -0500 To: Matt Helsley Cc: Trond Myklebust , "Serge E. Hallyn" , Linux Containers , linux-nfs@vger.kernel.org, Linux Kernel Mailing List , Chuck Lever , "Eric W. Biederman" , Linux Containers , Cedric Le Goater Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Message-ID: <20090107002024.GJ13785@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> <1231281732.4173.6.camel@heimdal.trondhjem.org> <1231286930.14345.196.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1231286930.14345.196.camel@localhost> 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: 1606 Lines: 35 On Tue, Jan 06, 2009 at 04:08:50PM -0800, Matt Helsley wrote: > On Tue, 2009-01-06 at 17:42 -0500, Trond Myklebust wrote: > > On Tue, 2009-01-06 at 15:58 -0600, Serge E. Hallyn wrote: > > > > > So should we use patch 2/4, plus (as someone - was it you? - suggested) > > > using a DEFAULT instead of init_utsname()->nodename when > > > current->utsname() == NULL? > > > > No. I'm don't think that 2/4 is correct either. Basically, 2/4 is saying > > that the container that first mounts the filesystem 'owns' it. However > > at the same time we know that the lifetime of the filesystem is in no > > way bounded by the lifetime of the container, and that's what gets you > > into trouble with 'umount' in the first place. > > > > IMO, the current code is the most correct approach, in that it assumes > > that the filesystems are owned by the 'init' namespace. > > IMHO This seems more incorrect than trying to use a more proximal > namespace. If it would be possible, for example, for the 'init' namespace to have no network interfaces at all, then it would be nicer to use a name that's at least been used with nfs at *some* point--just on the general principle of not leaking information to a domain that the user wouldn't expect it to. (Assuming it's unlikely anyone would consider init's utsname to be sensitive information, that's a minor point.) --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/