From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <linux-fsdevel@vger.kernel.org>, <xfs@oss.sgi.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] fs: fix iversion handling
Date: Tue, 3 Dec 2013 12:40:54 +0200 [thread overview]
Message-ID: <529DB536.7050008@panasas.com> (raw)
In-Reply-To: <20131203094507.GD4906@infradead.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
next prev parent reply other threads:[~2013-12-03 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131119151707.GA13412@infradead.org>
[not found] ` <20131202173636.GA17724@infradead.org>
2013-12-03 9:35 ` [PATCH] fs: fix iversion handling Boaz Harrosh
2013-12-03 9:45 ` Christoph Hellwig
2013-12-03 10:40 ` Boaz Harrosh [this message]
2013-12-03 20:54 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529DB536.7050008@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).