Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2018-01-02 Thread Jan Kara
On Fri 22-12-17 18:54:57, Jeff Layton wrote: > On Sat, 2017-12-23 at 10:14 +1100, NeilBrown wrote: > > > +#include > > > + > > > +/* > > > + * The change attribute (i_version) is mandated by NFSv4 and is mostly > > > for > > > + * knfsd, but is also used for other purposes (e.g. IMA). The

Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2018-01-02 Thread Jan Kara
On Fri 22-12-17 18:54:57, Jeff Layton wrote: > On Sat, 2017-12-23 at 10:14 +1100, NeilBrown wrote: > > > +#include > > > + > > > +/* > > > + * The change attribute (i_version) is mandated by NFSv4 and is mostly > > > for > > > + * knfsd, but is also used for other purposes (e.g. IMA). The

Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread Jeff Layton
On Sat, 2017-12-23 at 10:14 +1100, NeilBrown wrote: > On Fri, Dec 22 2017, Jeff Layton wrote: > > > From: Jeff Layton > > > > Add a documentation blob that explains what the i_version field is, how > > it is expected to work, and how it is currently implemented by various >

Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread Jeff Layton
On Sat, 2017-12-23 at 10:14 +1100, NeilBrown wrote: > On Fri, Dec 22 2017, Jeff Layton wrote: > > > From: Jeff Layton > > > > Add a documentation blob that explains what the i_version field is, how > > it is expected to work, and how it is currently implemented by various > > filesystems. > >

Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread NeilBrown
On Fri, Dec 22 2017, Jeff Layton wrote: > From: Jeff Layton > > Add a documentation blob that explains what the i_version field is, how > it is expected to work, and how it is currently implemented by various > filesystems. > > We already have inode_inc_iversion. Add several

Re: [PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread NeilBrown
On Fri, Dec 22 2017, Jeff Layton wrote: > From: Jeff Layton > > Add a documentation blob that explains what the i_version field is, how > it is expected to work, and how it is currently implemented by various > filesystems. > > We already have inode_inc_iversion. Add several other functions for

[PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread Jeff Layton
From: Jeff Layton Add a documentation blob that explains what the i_version field is, how it is expected to work, and how it is currently implemented by various filesystems. We already have inode_inc_iversion. Add several other functions for manipulating and accessing the

[PATCH v4 01/19] fs: new API for handling inode->i_version

2017-12-22 Thread Jeff Layton
From: Jeff Layton Add a documentation blob that explains what the i_version field is, how it is expected to work, and how it is currently implemented by various filesystems. We already have inode_inc_iversion. Add several other functions for manipulating and accessing the i_version counter. For