From: Trond Myklebust <trondmy@hammerspace.com>
To: "smayhew@redhat.com" <smayhew@redhat.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2] NFSv4: don't mark all open state for recovery when handling recallable state revoked flag
Date: Mon, 6 May 2019 16:36:02 +0000 [thread overview]
Message-ID: <f23e72bef69948d6ff5a9e306332deb7c6615e71.camel@hammerspace.com> (raw)
In-Reply-To: <20190506155905.16152-1-smayhew@redhat.com>
On Mon, 2019-05-06 at 11:59 -0400, Scott Mayhew wrote:
> Only delegations and layouts can be recalled, so it shouldn't be
> necessary to recover all opens when handling the status bit
> SEQ4_STATUS_RECALLABLE_STATE_REVOKED. We'll still wind up calling
> nfs41_open_expired() when a TEST_STATEID returns
> NFS4ERR_DELEG_REVOKED.
>
> Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> ---
> fs/nfs/delegation.c | 12 ++++++++++++
> fs/nfs/delegation.h | 1 +
> fs/nfs/nfs4state.c | 3 +--
> 3 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/delegation.c b/fs/nfs/delegation.c
> index 2f6b447cdd82..8b78274e3e56 100644
> --- a/fs/nfs/delegation.c
> +++ b/fs/nfs/delegation.c
> @@ -1033,6 +1033,18 @@ void
> nfs_mark_test_expired_all_delegations(struct nfs_client *clp)
> rcu_read_unlock();
> }
>
> +/**
> + * nfs_test_expired_all_delegations - test all delegations for a
> client
> + * @clp: nfs_client to process
> + *
> + * Helper for handling "recallable state revoked" status from
> server.
> + */
> +void nfs_test_expired_all_delegations(struct nfs_client *clp)
> +{
> + nfs_mark_test_expired_all_delegations(clp);
> + nfs4_schedule_state_manager(clp);
> +}
> +
> /**
> * nfs_reap_expired_delegations - reap expired delegations
> * @clp: nfs_client to process
> diff --git a/fs/nfs/delegation.h b/fs/nfs/delegation.h
> index 35b4b02c1ae0..5799777df5ec 100644
> --- a/fs/nfs/delegation.h
> +++ b/fs/nfs/delegation.h
> @@ -58,6 +58,7 @@ void nfs_delegation_mark_reclaim(struct nfs_client
> *clp);
> void nfs_delegation_reap_unclaimed(struct nfs_client *clp);
>
> void nfs_mark_test_expired_all_delegations(struct nfs_client *clp);
> +void nfs_test_expired_all_delegations(struct nfs_client *clp);
> void nfs_reap_expired_delegations(struct nfs_client *clp);
>
> /* NFSv4 delegation-related procedures */
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index 3de36479ed7a..7d0ee5a2aef9 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -2346,8 +2346,7 @@ static void
> nfs41_handle_recallable_state_revoked(struct nfs_client *clp)
> {
> /* FIXME: For now, we destroy all layouts. */
> pnfs_destroy_all_layouts(clp);
> - /* FIXME: For now, we test all delegations+open state+locks. */
> - nfs41_handle_some_state_revoked(clp);
> + nfs_test_expired_all_delegations(clp);
> dprintk("%s: Recallable state revoked on server %s!\n",
> __func__,
> clp->cl_hostname);
> }
Thank you!
Reviewed-by: Trond Myklebust <trond.myklebust@hammerspace.com>
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2019-05-06 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 15:59 [PATCH v2] NFSv4: don't mark all open state for recovery when handling recallable state revoked flag Scott Mayhew
2019-05-06 16:36 ` Trond Myklebust [this message]
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=f23e72bef69948d6ff5a9e306332deb7c6615e71.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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).