Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932357AbWHaQ04 (ORCPT ); Thu, 31 Aug 2006 12:26:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932363AbWHaQ04 (ORCPT ); Thu, 31 Aug 2006 12:26:56 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:56503 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932357AbWHaQ0y (ORCPT ); Thu, 31 Aug 2006 12:26:54 -0400 Date: Thu, 31 Aug 2006 17:26:28 +0100 From: Christoph Hellwig To: Trond Myklebust Cc: Shaya Potter , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, unionfs@fsl.cs.sunysb.edu Subject: Re: bug in nfs in 2.6.18-rc5? Message-ID: <20060831162628.GA23925@infradead.org> Mail-Followup-To: Christoph Hellwig , Trond Myklebust , Shaya Potter , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, unionfs@fsl.cs.sunysb.edu References: <44F6F80F.1000202@cs.columbia.edu> <1157040230.11347.31.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1157040230.11347.31.camel@localhost> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 728 Lines: 14 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. - 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/