From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: Re: ecryptfs Date: Mon, 07 Aug 2006 20:13:10 -0400 Message-ID: <1154995990.4585.0.camel@localhost.localdomain> References: <20060805140237.2226a9dc.akpm@osdl.org> <20060807161939.GC2950@us.ibm.com> <20060807163115.GA4028@us.ibm.com> <20060807172104.GA30519@filer.fsl.cs.sunysb.edu> <20060807224736.GI2883@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Josef Sipek , Andrew Morton , Christoph Hellwig , linux-fsdevel@vger.kernel.org Return-path: Received: from cs.columbia.edu ([128.59.16.20]:59603 "EHLO cs.columbia.edu") by vger.kernel.org with ESMTP id S932452AbWHHANX (ORCPT ); Mon, 7 Aug 2006 20:13:23 -0400 To: Michael Halcrow In-Reply-To: <20060807224736.GI2883@us.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 2006-08-07 at 17:47 -0500, Michael Halcrow wrote: > On Mon, Aug 07, 2006 at 01:21:04PM -0400, Josef Sipek wrote: > > On Mon, Aug 07, 2006 at 11:31:15AM -0500, Michael Halcrow wrote: > > ... > > > Here is where I am thinking about going with crossing lower mount > > > points. This patch makes sure that there is a 1-to-1 mapping in > > > inode numbers between the stacked inodes and the lower inodes. It > > > maintains the association by modifying the struct inode to include > > > a back pointer from the lower inode to the stacked inode. > > > > Do you maintain the inode numbers across mounts (of ecryptfs)? The > > patch doesn't look like it does. > > Nope; this patch just aims to make sure that stacked and lower inodes > maintain a 1-to-1 relationship. so that won't let your cross mount points.... i.e. the 2 underlying mountpoints can have the same inode numbers, couldn't they?