From: Christoph Hellwig Subject: Re: bug in nfs in 2.6.18-rc5? Date: Thu, 31 Aug 2006 17:27:45 +0100 Message-ID: <20060831162745.GB23925@infradead.org> References: <44F6F80F.1000202@cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, unionfs@fsl.cs.sunysb.edu Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:61111 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932363AbWHaQ2G (ORCPT ); Thu, 31 Aug 2006 12:28:06 -0400 To: Shaya Potter Content-Disposition: inline In-Reply-To: <44F6F80F.1000202@cs.columbia.edu> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Aug 31, 2006 at 10:54:07AM -0400, Shaya Potter wrote: > so I'm trying to use unionfs, cachefs and nfs, as cachefs is 2.6.18-rc5 > right now, thats what I'm testing, but I hit an oops. > > basically unionfs's lookup does a "lookup_one_len()" on the underlying fs. And there you have the bug already. unionfs must not do this, and given the past discussion on this the unionfs developers should know that very well :)