From: Trond Myklebust Subject: Re: [PATCH 04/22][RFC] Unionfs: Common file operations Date: Fri, 01 Sep 2006 18:57:20 -0400 Message-ID: <1157151440.5628.42.camel@localhost> References: <20060901013512.GA5788@fsl.cs.sunysb.edu> <20060901014138.GE5788@fsl.cs.sunysb.edu> <1157149200.5628.38.camel@localhost> <1157150161.4398.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Josef Sipek , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, akpm@osdl.org, viro@ftp.linux.org.uk Return-path: Received: from pat.uio.no ([129.240.10.4]:4336 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S1751106AbWIAW5b (ORCPT ); Fri, 1 Sep 2006 18:57:31 -0400 To: Shaya Potter In-Reply-To: <1157150161.4398.4.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 2006-09-01 at 18:36 -0400, Shaya Potter wrote: > On Fri, 2006-09-01 at 18:20 -0400, Trond Myklebust wrote: > > > Race! You cannot open an underlying NFS file by name after it has been > > looked up: you have no guarantee that it hasn't been renamed. > > In a unionfs case that's not an issue. Nothing else is allowed to use > the backing store (i.e. the nfs fs) while unionfs is using it, so there > shouldn't be a renaming issue. How are you enforcing that on the server? -- VGER BF report: H 2.77556e-16