From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: NFS4 crack Date: Sun, 18 Sep 2005 10:36:15 -0400 Message-ID: <20050918143615.GA3428@fieldses.org> References: <20050918102100.GA23463@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: Received: from dsl093-002-214.det1.dsl.speakeasy.net ([66.93.2.214]:18347 "EHLO pickle.fieldses.org") by vger.kernel.org with ESMTP id S932073AbVIROg2 (ORCPT ); Sun, 18 Sep 2005 10:36:28 -0400 To: Christoph Hellwig Content-Disposition: inline In-Reply-To: <20050918102100.GA23463@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sun, Sep 18, 2005 at 12:21:00PM +0200, Christoph Hellwig wrote: > I've recently turned on NFS4 server support accidentally, just to get > error messages like: > > "NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist" > > To my horror I found out that this comes from kernel code, which messes > with a hardcoded directory, completelyu ingoring any namespace or other > uses issues. As long as all nfsd threads are in the same namespace, I don't see any namespace issues. What am I missing? > The fs handling in fs/nfs/nfs4recovery.c is rather broken in addition. For example? --b.