linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Linux NFS Mailing <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFSDv4: use export cache flushtime for changeid on V4ROOT objects.
Date: Mon, 30 Jan 2017 10:35:17 -0500	[thread overview]
Message-ID: <20170130153517.GC24786@fieldses.org> (raw)
In-Reply-To: <87mve9rs0z.fsf@notabene.neil.brown.name>

On Mon, Jan 30, 2017 at 05:17:00PM +1100, NeilBrown wrote:
> 
> If you change the set of filesystems that are exported, then
> the contents of various directories in the NFSv4 pseudo-root
> is likely to change.  However the change-id of those
> directories is currently tied to the underlying directory,
> so the clinet may not see the changes in a timely fashion.

Oh, good catch.

> This patch changes the change-id number to be derived from the
> "flush_time" of the export cache.  Whenever any changes are
> made to the set of exported filesystems, this flush_time is
> updated.  The result is that clients see changes to the set
> of exported filesystems much more quickly, often immediately.

And, a clever solution, as usual....

I wonder if it's completely right yet, though.  Off the top of my head:
can't the client see the new flush time before it sees the new contents?
If so, a client that caches both during that window could cache the old
contents indefinitely.

--b.

> 
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
>  fs/nfsd/nfs4xdr.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 8fae53ce21d1..dbff0122b784 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -1966,9 +1966,13 @@ nfsd4_decode_compound(struct nfsd4_compoundargs *argp)
>  	DECODE_TAIL;
>  }
>  
> -static __be32 *encode_change(__be32 *p, struct kstat *stat, struct inode *inode)
> +static __be32 *encode_change(__be32 *p, struct kstat *stat, struct inode *inode,
> +			     struct svc_export *exp)
>  {
> -	if (IS_I_VERSION(inode)) {
> +	if (exp->ex_flags & NFSEXP_V4ROOT) {
> +		*p++ = cpu_to_be32(convert_to_wallclock(exp->cd->flush_time));
> +		*p++ = 0;
> +	} else if (IS_I_VERSION(inode)) {
>  		p = xdr_encode_hyper(p, inode->i_version);
>  	} else {
>  		*p++ = cpu_to_be32(stat->ctime.tv_sec);
> @@ -2490,7 +2494,7 @@ nfsd4_encode_fattr(struct xdr_stream *xdr, struct svc_fh *fhp,
>  		p = xdr_reserve_space(xdr, 8);
>  		if (!p)
>  			goto out_resource;
> -		p = encode_change(p, &stat, d_inode(dentry));
> +		p = encode_change(p, &stat, d_inode(dentry), exp);
>  	}
>  	if (bmval0 & FATTR4_WORD0_SIZE) {
>  		p = xdr_reserve_space(xdr, 8);
> -- 
> 2.11.0
> 



  reply	other threads:[~2017-01-30 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  6:17 [PATCH] NFSDv4: use export cache flushtime for changeid on V4ROOT objects NeilBrown
2017-01-30 15:35 ` J. Bruce Fields [this message]
2017-01-30 22:28   ` NeilBrown
2017-01-31 14:38     ` J. Bruce Fields
2017-02-06 21:07       ` NeilBrown
2017-02-06 22:28         ` 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=20170130153517.GC24786@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.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).