From: Shaya Potter <spotter@cs.columbia.edu>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: ecryptfs
Date: Mon, 07 Aug 2006 20:13:10 -0400 [thread overview]
Message-ID: <1154995990.4585.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20060807224736.GI2883@us.ibm.com>
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?
next prev parent reply other threads:[~2006-08-08 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060805140237.2226a9dc.akpm@osdl.org>
[not found] ` <20060807161939.GC2950@us.ibm.com>
2006-08-07 16:31 ` ecryptfs Michael Halcrow
2006-08-07 17:21 ` ecryptfs Josef Sipek
2006-08-07 22:47 ` ecryptfs Michael Halcrow
2006-08-08 0:13 ` Shaya Potter [this message]
2006-08-08 14:31 ` ecryptfs Michael Halcrow
2006-08-08 15:10 ` ecryptfs Shaya Potter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154995990.4585.0.camel@localhost.localdomain \
--to=spotter@cs.columbia.edu \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).