From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Halcrow Subject: Re: [PATCH] fsstack: fsstack_copy_inode_size locking Date: Mon, 30 Jun 2008 16:49:01 -0500 Message-ID: <20080630214901.GA8900@halcrowt61p.austin.ibm.com> References: <200806301819.m5UIJRhv030310@agora.fsl.cs.sunysb.edu> Reply-To: Michael Halcrow Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Hugh Dickins , Christoph Hellwig , Andrew Morton , hooanon05@yahoo.co.jp, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Erez Zadok Return-path: Received: from e6.ny.us.ibm.com ([32.97.182.146]:44555 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933806AbYF3VqZ (ORCPT ); Mon, 30 Jun 2008 17:46:25 -0400 Content-Disposition: inline In-Reply-To: <200806301819.m5UIJRhv030310@agora.fsl.cs.sunysb.edu> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.