From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: bug in nfs in 2.6.18-rc5?
Date: Thu, 31 Aug 2006 17:26:28 +0100
Message-ID: <20060831162628.GA23925@infradead.org>
References: <44F6F80F.1000202@cs.columbia.edu> <1157040230.11347.31.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Shaya Potter <spotter@cs.columbia.edu>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	unionfs@fsl.cs.sunysb.edu
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from pentafluge.infradead.org ([213.146.154.40]:56503 "EHLO
	pentafluge.infradead.org") by vger.kernel.org with ESMTP
	id S932357AbWHaQ0y (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 31 Aug 2006 12:26:54 -0400
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Content-Disposition: inline
In-Reply-To: <1157040230.11347.31.camel@localhost>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Thu, Aug 31, 2006 at 12:03:50PM -0400, Trond Myklebust wrote:
> If we're to provide the ability for unionfs to use lookup_one_len() on
> NFS, then we will have to error out whenever we hit a case where we
> should be creating a new mountpoint. Is that acceptable?

Not at all.  unionfs will have to pass down proper lookup intents.
The ecryptfs developers have started looking into making that work
with stackable filesystems, and the unionfs developers should follow
that effort.