From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
NFS list <linux-nfs@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH] fs: fix iversion handling
Date: Tue, 3 Dec 2013 01:45:07 -0800 [thread overview]
Message-ID: <20131203094507.GD4906@infradead.org> (raw)
In-Reply-To: <529DA5C6.7040403@panasas.com>
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
next prev parent reply other threads:[~2013-12-03 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 15:17 [PATCH] fs: fix iversion handling Christoph Hellwig
2013-12-02 17:36 ` Christoph Hellwig
2013-12-02 22:05 ` Andreas Dilger
2013-12-03 9:39 ` Christoph Hellwig
2013-12-02 22:11 ` Jan Kara
[not found] ` <20131202173636.GA17724-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-12-03 9:35 ` Boaz Harrosh
2013-12-03 9:45 ` Christoph Hellwig [this message]
[not found] ` <20131203094507.GD4906-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-12-03 10:40 ` Boaz Harrosh
[not found] ` <529DB536.7050008-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2013-12-03 20:54 ` J. Bruce Fields
2013-12-02 23:25 ` Dave Chinner
2013-12-04 21:25 ` Ben Myers
2013-12-04 22:01 ` Chris Mason
2013-12-05 22:37 ` Ben Myers
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=20131203094507.GD4906@infradead.org \
--to=hch@infradead.org \
--cc=bharrosh@panasas.com \
--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).