From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] fs: fix iversion handling Date: Tue, 3 Dec 2013 01:45:07 -0800 Message-ID: <20131203094507.GD4906@infradead.org> References: <20131119151707.GA13412@infradead.org> <20131202173636.GA17724@infradead.org> <529DA5C6.7040403@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , linux-fsdevel@vger.kernel.org, NFS list , xfs@oss.sgi.com To: Boaz Harrosh Return-path: Content-Disposition: inline In-Reply-To: <529DA5C6.7040403@panasas.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Tue, Dec 03, 2013 at 11:35:02AM +0200, Boaz Harrosh wrote: > Hi Christoph > > What happens with all other filesystems exported under KNFSD? > > As I understand inode_inc_iversion() is used in NFSv4 and up, > what will increment the inode-version on changed attributes > for them? It's used by the filesystem for the change attribute that NFSDd can optionally use. Most filesystsems don't support it and work okay enough when NFS exported. No other filesystem will need to adopt for this patch specificly, given that no other filesystem uses this infrastructure. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs