From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: NFS4 crack
Date: Mon, 19 Sep 2005 10:07:15 -0400
Message-ID: <20050919140715.GC20732@fieldses.org>
References: <20050918102100.GA23463@lst.de> <20050918143615.GA3428@fieldses.org> <20050919103547.GA8998@lst.de> <20050919133528.GA20732@fieldses.org> <20050919133921.GA12208@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: akpm@osdl.org, neilb@cse.unsw.edu.au, andros@citi.umich.edu,
	linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from dsl093-002-214.det1.dsl.speakeasy.net ([66.93.2.214]:34184 "EHLO
	pickle.fieldses.org") by vger.kernel.org with ESMTP id S932415AbVISOHV
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 19 Sep 2005 10:07:21 -0400
To: Christoph Hellwig <hch@lst.de>
Content-Disposition: inline
In-Reply-To: <20050919133921.GA12208@lst.de>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Mon, Sep 19, 2005 at 03:39:21PM +0200, Christoph Hellwig wrote:
> On Mon, Sep 19, 2005 at 09:35:28AM -0400, J. Bruce Fields wrote:
> > On Mon, Sep 19, 2005 at 12:35:47PM +0200, Christoph Hellwig wrote:
> > > Namespaces issues above was meant as kernel can't assume namespace at
> > > all, not even thinking about multiple namespaces which makes it even
> > > more wrong.  Who sais I allow the kernel to mess with
> > > /var/lib/nfs/v4recover?
> > 
> > It's run-time configurable if you don't like the default.
> > 
> > > Who tells any userspace process is even in the same namespace as the
> > > nfs threads to create the directories?
> > 
> > No userspace process is likely to care, except maybe for debugging
> > purposes.  This isn't a userspace<->kernel interface, it's just a way to
> > store some information on disk so nfsd can find it again on next boot.
> 
> Again,
> 
> FILENAMES ARE POLICY AND HAVE NO BUSINESS IN THE KERNEL

What problem does this create in this case?

The "hardcoded" path is just a default for a value that can be modified
at runtime.  We could default to the empty string, I suppose, and make
sure the path is set in the nfs init scripts.

--b.