Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 09/14] NFS: Force server to drop NFSv4 state
Date: Mon, 21 May 2012 12:08:44 -0400	[thread overview]
Message-ID: <20120521160844.GH24299@fieldses.org> (raw)
In-Reply-To: <20120518220632.774.79191.stgit@degas.1015granger.net>

On Fri, May 18, 2012 at 06:06:33PM -0400, Chuck Lever wrote:
> A SETCLIENTID boot verifier is nothing more than the client's boot
> timestamp.  An NFSv4 server is obligated to wipe all NFSv4 state for
> an NFS client when the client presents an updated SETCLIENTID boot
> verifier.  This is how servers detect client reboots.
> 
> nfs4_reset_all_state() refreshes our client's boot verifier to trigger
> a server to wipe this client's state.  This function is invoked when
> an NFSv4.1 server reports that it has revoked some or all of a
> client's NFSv4 state.
> 
> Soon we want to get rid of the per-nfs_client cl_boot_time field,

OK, I guess you don't need it if you never intend to send a callback
update or anything?

> however.  Without cl_boot_time, our NFS client will need to find a
> different way to force the server to purge the client's NFSv4 state.
> 
> Because these verifiers are opaque (ie, the server doesn't know or
> care that they happen to be timestamps), we can do force the server
> to wipe NFSv4 state by using the same trick we use now, but then
> immediately afterwards establish a fresh client ID using the old boot
> verifier again.
> 
> Hopefully there are no extra paranoid server implementations that keep
> track of the client's boot verifiers and prevent clients from reusing
> a previous one.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> 
>  fs/nfs/nfs4_fs.h   |    1 +
>  fs/nfs/nfs4proc.c  |    9 +++++++--
>  fs/nfs/nfs4state.c |   13 +++++++++++--
>  3 files changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/nfs/nfs4_fs.h b/fs/nfs/nfs4_fs.h
> index 03d3ff0..f164c73 100644
> --- a/fs/nfs/nfs4_fs.h
> +++ b/fs/nfs/nfs4_fs.h
> @@ -24,6 +24,7 @@ enum nfs4_client_state {
>  	NFS4CLNT_RECALL_SLOT,
>  	NFS4CLNT_LEASE_CONFIRM,
>  	NFS4CLNT_SERVER_SCOPE_MISMATCH,
> +	NFS4CLNT_PURGE_STATE,
>  };
>  
>  enum nfs4_session_state {
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 73cfd9e..c56d547 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -3937,8 +3937,13 @@ static void nfs4_construct_boot_verifier(struct nfs_client *clp,
>  {
>  	__be32 verf[2];
>  
> -	verf[0] = (__be32)clp->cl_boot_time.tv_sec;
> -	verf[1] = (__be32)clp->cl_boot_time.tv_nsec;
> +	if (test_bit(NFS4CLNT_PURGE_STATE, &clp->cl_state)) {
> +		verf[0] = (__be32)CURRENT_TIME.tv_sec;
> +		verf[1] = (__be32)CURRENT_TIME.tv_nsec;

I suppose it's pretty unlikely this could happen within a jiffy of
setting cl_boot_time?

Would it be simpler to use some special value (all-zeros?) instead?

--b.

> +	} else {
> +		verf[0] = (__be32)clp->cl_boot_time.tv_sec;
> +		verf[1] = (__be32)clp->cl_boot_time.tv_nsec;
> +	}
>  	memcpy(bootverf->data, verf, sizeof(bootverf->data));
>  }
>  
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index f8c06de..32cce4a 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -1615,7 +1615,7 @@ void nfs41_handle_recall_slot(struct nfs_client *clp)
>  static void nfs4_reset_all_state(struct nfs_client *clp)
>  {
>  	if (test_and_set_bit(NFS4CLNT_LEASE_EXPIRED, &clp->cl_state) == 0) {
> -		clp->cl_boot_time = CURRENT_TIME;
> +		set_bit(NFS4CLNT_PURGE_STATE, &clp->cl_state);
>  		nfs4_state_start_reclaim_nograce(clp);
>  		nfs4_schedule_state_manager(clp);
>  	}
> @@ -1631,7 +1631,6 @@ static void nfs41_handle_server_reboot(struct nfs_client *clp)
>  
>  static void nfs41_handle_state_revoked(struct nfs_client *clp)
>  {
> -	/* Temporary */
>  	nfs4_reset_all_state(clp);
>  }
>  
> @@ -1652,6 +1651,10 @@ void nfs41_handle_sequence_flag_errors(struct nfs_client *clp, u32 flags)
>  {
>  	if (!flags)
>  		return;
> +
> +	dprintk("%s: \"%s\" (client ID %llx) flags=0x%08x\n",
> +		__func__, clp->cl_hostname, clp->cl_clientid, flags);
> +
>  	if (flags & SEQ4_STATUS_RESTART_RECLAIM_NEEDED)
>  		nfs41_handle_server_reboot(clp);
>  	if (flags & (SEQ4_STATUS_EXPIRED_ALL_STATE_REVOKED |
> @@ -1762,6 +1765,12 @@ static void nfs4_state_manager(struct nfs_client *clp)
>  
>  	/* Ensure exclusive access to NFSv4 state */
>  	do {
> +		if (test_bit(NFS4CLNT_PURGE_STATE, &clp->cl_state)) {
> +			nfs4_reclaim_lease(clp);
> +			clear_bit(NFS4CLNT_PURGE_STATE, &clp->cl_state);
> +			set_bit(NFS4CLNT_LEASE_EXPIRED, &clp->cl_state);
> +		}
> +
>  		if (test_and_clear_bit(NFS4CLNT_LEASE_EXPIRED, &clp->cl_state)) {
>  			/* We're going to have to re-establish a clientid */
>  			status = nfs4_reclaim_lease(clp);
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-05-21 16:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 22:05 [PATCH 00/14] UCS pre-requisites for 3.5 Chuck Lever
2012-05-18 22:05 ` [PATCH 01/14] NFS: Fix comment misspelling in struct nfs_client definition Chuck Lever
2012-05-18 22:05 ` [PATCH 02/14] NFS: Use proper naming conventions for NFSv4.1 server scope fields Chuck Lever
2012-05-19 21:08   ` Myklebust, Trond
2012-05-18 22:05 ` [PATCH 03/14] NFS: Use proper naming conventions for nfs_client.impl_id field Chuck Lever
2012-05-21 15:06   ` Adamson, Dros
2012-05-18 22:05 ` [PATCH 04/14] NFS: Use proper naming conventions for the nfs_client.net field Chuck Lever
2012-05-18 22:05 ` [PATCH 05/14] NFS: Clean up return code checking in nfs4_proc_exchange_id() Chuck Lever
2012-05-21 15:10   ` Adamson, Dros
2012-05-21 15:19     ` Chuck Lever
2012-05-18 22:06 ` [PATCH 06/14] NFS: Remove nfs_unique_id Chuck Lever
2012-05-18 22:06 ` [PATCH 07/14] NFS: Don't swap bytes in nfs4_construct_boot_verifier() Chuck Lever
2012-05-21 15:40   ` J. Bruce Fields
2012-05-21 15:47     ` Chuck Lever
2012-05-21 15:51       ` J. Bruce Fields
2012-05-18 22:06 ` [PATCH 08/14] NFS: Add NFSDBG_STATE Chuck Lever
2012-05-18 22:06 ` [PATCH 09/14] NFS: Force server to drop NFSv4 state Chuck Lever
2012-05-21 16:08   ` J. Bruce Fields [this message]
2012-05-21 16:11     ` J. Bruce Fields
2012-05-21 16:11     ` Chuck Lever
2012-05-21 16:16       ` J. Bruce Fields
2012-05-21 16:24         ` Chuck Lever
2012-05-21 16:49           ` Myklebust, Trond
2012-05-18 22:06 ` [PATCH 10/14] NFS: Always use the same SETCLIENTID boot verifier Chuck Lever
2012-05-18 22:06 ` [PATCH 11/14] NFS: Refactor nfs_get_client(): add nfs_found_client() Chuck Lever
2012-05-18 22:06 ` [PATCH 12/14] NFS: Refactor nfs_get_client(): initialize nfs_client Chuck Lever
2012-05-18 22:07 ` [PATCH 13/14] NFS: Add nfs_client behavior flags Chuck Lever
2012-05-18 22:07 ` [PATCH 14/14] NFS: EXCHANGE_ID should save the server major and minor ID Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2012-05-22  2:44 [PATCH 00/14 v2] UCS pre-requisites for 3.5 Chuck Lever
2012-05-22  2:45 ` [PATCH 09/14] NFS: Force server to drop NFSv4 state Chuck Lever

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=20120521160844.GH24299@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.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