[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080630214901.GA8900@halcrowt61p.austin.ibm.com>
Date: Mon, 30 Jun 2008 16:49:01 -0500
From: Michael Halcrow <mhalcrow@...ibm.com>
To: Erez Zadok <ezk@...sunysb.edu>
Cc: Hugh Dickins <hugh@...itas.com>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
hooanon05@...oo.co.jp, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fsstack: fsstack_copy_inode_size locking
On Mon, Jun 30, 2008 at 02:19:27PM -0400, Erez Zadok wrote:
> BTW, ecryptfs may have a problem with this, b/c it uses
> i_size_read/write b/t the lower and upper inodes. If some
> filesystems have a different interpretation for i_size, then
> stacking ecryptfs on top of them could be an issue. Mike?
eCryptfs depends on the results of i_size_read() on the lower inode
when it needs to interpolate the filesize when the metadata is stored
in the lower file's xattr region.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists