[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 04 Mar 2017 10:55:04 +1100
From: NeilBrown <neil@...wn.name>
To: Jeff Layton <jlayton@...hat.com>, linux-fsdevel@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-xfs@...r.kernel.org
Subject: Re: [RFC PATCH v1 11/30] fs: new API for handling i_version
On Wed, Dec 21 2016, Jeff Layton wrote:
> We already have inode_inc_iversion. Add inode_set_iversion,
> inode_get_iversion, inode_cmp_iversion and inode_iversion_need_inc.
This list of added interfaces is incomplete.
And some of these interfaces could really use some justification up
front.
You later add a "force" parameter to inode_inc_version.
Why not do that up front here?
> +
> +/**
> + * inode_get_iversion - read i_version for later use
> + * @inode: inode from which i_version should be read
> + *
> + * Read the inode i_version counter. This should be used by callers that wish
> + * to store the returned i_version for later comparison.
> + */
> +static inline u64
> +inode_get_iversion(const struct inode *inode)
> +{
> + return inode_get_iversion_raw(inode);
> +}
I don't understand why this can use the _raw version rather than the
_read version.
Surely you need to know about any changes after this read.
Thanks,
NeilBrown
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists