Linux NFS development
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
	Olga Kornievskaia <kolga@netapp.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are revoked
Date: Wed, 5 Nov 2014 09:49:58 -0500	[thread overview]
Message-ID: <545A3916.1050906@Netapp.com> (raw)
In-Reply-To: <1415144188-17193-2-git-send-email-trond.myklebust@primarydata.com>

Hey Trond,

On 11/04/2014 06:36 PM, Trond Myklebust wrote:
> NFSv4.x (x>0) requires us to call TEST_STATEID+FREE_STATEID if a stateid is
> revoked. We will currently fail to do this if the stateid is a delegation.
>
> http://lkml.kernel.org/r/CAN-5tyHwG=Cn2Q9KsHWadewjpTTy_K26ee+UnSvHvG4192p-Xw@mail.gmail.com
> Cc: stable@vger.kernel.org
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
>  fs/nfs/nfs4proc.c | 8 --------
>  1 file changed, 8 deletions(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index d8f352d8c75f..6cf49af3092d 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -370,11 +370,6 @@ static int nfs4_handle_exception(struct nfs_server *server, int errorcode, struc
>  		case -NFS4ERR_DELEG_REVOKED:
>  		case -NFS4ERR_ADMIN_REVOKED:
>  		case -NFS4ERR_BAD_STATEID:
> -			if (inode != NULL && nfs4_have_delegation(inode, FMODE_READ)) {
> -				nfs_remove_bad_delegation(inode);
> -				exception->retry = 1;
> -				break;
> -			}
>  			if (state == NULL)
>  				break;
>  			ret = nfs4_schedule_stateid_recovery(server, state);
> @@ -4849,9 +4844,6 @@ nfs4_async_handle_error(struct rpc_task *task, const struct nfs_server *server,
>  		case -NFS4ERR_DELEG_REVOKED:
>  		case -NFS4ERR_ADMIN_REVOKED:
>  		case -NFS4ERR_BAD_STATEID:
> -			if (state == NULL)
> -				break;
> -			nfs_remove_bad_delegation(state->inode);

Does filelayout_async_handle_error() need to be updated in the same way?  They are the only remaining caller of nfs_remove_bad_delegation().

Thanks,
Anna

>  		case -NFS4ERR_OPENMODE:
>  			if (state == NULL)
>  				break;


  parent reply	other threads:[~2014-11-05 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 23:36 [PATCH 1/3] NFSv4: Ensure that we remove delegations before recovering Trond Myklebust
2014-11-04 23:36 ` [PATCH 2/3] NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are revoked Trond Myklebust
2014-11-04 23:36   ` [PATCH 3/3] NFS: Don't try to reclaim delegation open state if recovery failed Trond Myklebust
2014-11-05 14:49   ` Anna Schumaker [this message]
2014-11-05 14:53     ` [PATCH 2/3] NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are revoked Trond Myklebust

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=545A3916.1050906@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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