xfs
[Top] [All Lists]

Re: [PATCH] fs: fix iversion handling

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH] fs: fix iversion handling
From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
Date: Tue, 3 Dec 2013 12:40:54 +0200
Cc: <linux-fsdevel@xxxxxxxxxxxxxxx>, <xfs@xxxxxxxxxxx>, NFS list <linux-nfs@xxxxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131203094507.GD4906@xxxxxxxxxxxxx>
References: <20131119151707.GA13412@xxxxxxxxxxxxx> <20131202173636.GA17724@xxxxxxxxxxxxx> <529DA5C6.7040403@xxxxxxxxxxx> <20131203094507.GD4906@xxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
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

<Prev in Thread] Current Thread [Next in Thread>