Subject: Re: [PATCH 04/22][RFC] Unionfs: Common file operations
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: Josef Sipek <jsipek@cs.sunysb.edu>, linux-kernel@vger.kernel.org,
       linux-fsdevel@vger.kernel.org, hch@infradead.org, akpm@osdl.org,
       viro@ftp.linux.org.uk
In-Reply-To: <1157150161.4398.4.camel@localhost.localdomain>
References: <20060901013512.GA5788@fsl.cs.sunysb.edu>
	 <20060901014138.GE5788@fsl.cs.sunysb.edu>
	 <1157149200.5628.38.camel@localhost>
	 <1157150161.4398.4.camel@localhost.localdomain>
Content-Type: text/plain
Date: Fri, 01 Sep 2006 18:57:20 -0400
Message-Id: <1157151440.5628.42.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 766
Lines: 21

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
-
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/