| To: | Boaz Harrosh <bharrosh@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] fs: fix iversion handling |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 3 Dec 2013 01:45:07 -0800 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, NFS list <linux-nfs@xxxxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <529DA5C6.7040403@xxxxxxxxxxx> |
| References: | <20131119151707.GA13412@xxxxxxxxxxxxx> <20131202173636.GA17724@xxxxxxxxxxxxx> <529DA5C6.7040403@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 05/10] xfs: introduce xlog_copy_iovec, Christoph Hellwig |
|---|---|
| Next by Date: | Re: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250), Emmanuel Lacour |
| Previous by Thread: | Re: [PATCH] fs: fix iversion handling, Boaz Harrosh |
| Next by Thread: | Re: [PATCH] fs: fix iversion handling, Boaz Harrosh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |