From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from static-209-166-131-148.expedient.com ([209.166.131.148]:35449 "EHLO natasha.panasas.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752771Ab3LCKlZ (ORCPT ); Tue, 3 Dec 2013 05:41:25 -0500 Message-ID: <529DB536.7050008@panasas.com> Date: Tue, 3 Dec 2013 12:40:54 +0200 From: Boaz Harrosh MIME-Version: 1.0 To: Christoph Hellwig CC: , , NFS list Subject: Re: [PATCH] fs: fix iversion handling References: <20131119151707.GA13412@infradead.org> <20131202173636.GA17724@infradead.org> <529DA5C6.7040403@panasas.com> <20131203094507.GD4906@infradead.org> In-Reply-To: <20131203094507.GD4906@infradead.org> Content-Type: text/plain; charset="UTF-8" Sender: linux-nfs-owner@vger.kernel.org List-ID: On 12/03/2013 11:45 AM, Christoph Hellwig wrote: > 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. > OK Thanks, I did not know that. I assumed change-attribute is naturally supported. I will look at ext4 example and wire up exofs. Because it is very important for me to support the change-attribute properly. Thanks you Boaz From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 7CCBD7F59 for ; Tue, 3 Dec 2013 04:41:27 -0600 (CST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id 23F15AC001 for ; Tue, 3 Dec 2013 02:41:23 -0800 (PST) Received: from natasha.panasas.com (natasha.panasas.com [209.166.131.148]) by cuda.sgi.com with ESMTP id 0XalZjWEggC79ABb for ; Tue, 03 Dec 2013 02:41:21 -0800 (PST) Message-ID: <529DB536.7050008@panasas.com> Date: Tue, 3 Dec 2013 12:40:54 +0200 From: Boaz Harrosh MIME-Version: 1.0 Subject: Re: [PATCH] fs: fix iversion handling References: <20131119151707.GA13412@infradead.org> <20131202173636.GA17724@infradead.org> <529DA5C6.7040403@panasas.com> <20131203094507.GD4906@infradead.org> In-Reply-To: <20131203094507.GD4906@infradead.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Christoph Hellwig Cc: linux-fsdevel@vger.kernel.org, NFS list , xfs@oss.sgi.com On 12/03/2013 11:45 AM, Christoph Hellwig wrote: > 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. > OK Thanks, I did not know that. I assumed change-attribute is naturally supported. I will look at ext4 example and wire up exofs. Because it is very important for me to support the change-attribute properly. Thanks you Boaz _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: [PATCH] fs: fix iversion handling Date: Tue, 3 Dec 2013 12:40:54 +0200 Message-ID: <529DB536.7050008@panasas.com> References: <20131119151707.GA13412@infradead.org> <20131202173636.GA17724@infradead.org> <529DA5C6.7040403@panasas.com> <20131203094507.GD4906@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: , , NFS list To: Christoph Hellwig Return-path: In-Reply-To: <20131203094507.GD4906-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On 12/03/2013 11:45 AM, Christoph Hellwig wrote: > 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. > OK Thanks, I did not know that. I assumed change-attribute is naturally supported. I will look at ext4 example and wire up exofs. Because it is very important for me to support the change-attribute properly. Thanks you Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html