linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSv4: always set NFS_LOCK_LOST when a lock is lost.
Date: Wed, 20 Dec 2017 08:15:25 +1100	[thread overview]
Message-ID: <87bmiul8r6.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <87r2rzo8qi.fsf@notabene.neil.brown.name>

[-- Attachment #1: Type: text/plain, Size: 4596 bytes --]

On Wed, Dec 13 2017, NeilBrown wrote:

> There are 2 comments in the NFSv4 code which suggest that
> SIGLOST should possibly be sent to a process.  In these
> cases a lock has been lost.
> The current practice is to set NFS_LOCK_LOST so that
> read/write returns EIO when a lock is lost.
> So change these comments to code when sets NFS_LOCK_LOST.
>
> One case is when lock recovery after apparent server restart
> fails with NFS4ERR_DENIED, NFS4ERR_RECLAIM_BAD, or
> NFS4ERRO_RECLAIM_CONFLICT.  The other case is when a lock
> attempt as part of lease recovery fails with NFS4ERR_DENIED.
>
> In an ideal world, these should not happen.  However I have
> a packet trace showing an NFSv4.1 session getting
> NFS4ERR_BADSESSION after an extended network parition.  The
> NFSv4.1 client treats this like server reboot until/unless
> it get NFS4ERR_NO_GRACE, in which case it switches over to
> "nograce" recovery mode.  In this network trace, the client
> attempts to recover a lock and the server (incorrectly)
> reports NFS4ERR_DENIED rather than NFS4ERR_NO_GRACE.  This
> leads to the ineffective comment and the client then
> continues to write using the OPEN stateid.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
>
> Note that I have not tested this as I do not have direct access to a
> faulty NFS server.  Once I get confirmation I will provide an update.

Hi,
 I have now received confirmation that this change does fix the locking
 behavior in this case where the server is returning the wrong error
 code.

Thanks,
NeilBrown


>
> NeilBrown
>
>  fs/nfs/nfs4proc.c  | 12 ++++++++----
>  fs/nfs/nfs4state.c |  5 ++++-
>  2 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 56fa5a16e097..083802f7a1e9 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -2019,7 +2019,7 @@ static int nfs4_open_reclaim(struct nfs4_state_owner *sp, struct nfs4_state *sta
>  	return ret;
>  }
>  
> -static int nfs4_handle_delegation_recall_error(struct nfs_server *server, struct nfs4_state *state, const nfs4_stateid *stateid, int err)
> +static int nfs4_handle_delegation_recall_error(struct nfs_server *server, struct nfs4_state *state, const nfs4_stateid *stateid, struct file_lock *fl, int err)
>  {
>  	switch (err) {
>  		default:
> @@ -2066,7 +2066,11 @@ static int nfs4_handle_delegation_recall_error(struct nfs_server *server, struct
>  			return -EAGAIN;
>  		case -ENOMEM:
>  		case -NFS4ERR_DENIED:
> -			/* kill_proc(fl->fl_pid, SIGLOST, 1); */
> +			if (fl) {
> +				struct nfs4_lock_state *lsp = fl->fl_u.nfs4_fl.owner;
> +				if (lsp)
> +					set_bit(NFS_LOCK_LOST, &lsp->ls_flags);
> +			}
>  			return 0;
>  	}
>  	return err;
> @@ -2102,7 +2106,7 @@ int nfs4_open_delegation_recall(struct nfs_open_context *ctx,
>  		err = nfs4_open_recover_helper(opendata, FMODE_READ);
>  	}
>  	nfs4_opendata_put(opendata);
> -	return nfs4_handle_delegation_recall_error(server, state, stateid, err);
> +	return nfs4_handle_delegation_recall_error(server, state, stateid, NULL, err);
>  }
>  
>  static void nfs4_open_confirm_prepare(struct rpc_task *task, void *calldata)
> @@ -6739,7 +6743,7 @@ int nfs4_lock_delegation_recall(struct file_lock *fl, struct nfs4_state *state,
>  	if (err != 0)
>  		return err;
>  	err = _nfs4_do_setlk(state, F_SETLK, fl, NFS_LOCK_NEW);
> -	return nfs4_handle_delegation_recall_error(server, state, stateid, err);
> +	return nfs4_handle_delegation_recall_error(server, state, stateid, fl, err);
>  }
>  
>  struct nfs_release_lockowner_data {
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index e4f4a09ed9f4..91a4d4eeb235 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -1482,6 +1482,7 @@ static int nfs4_reclaim_locks(struct nfs4_state *state, const struct nfs4_state_
>  	struct inode *inode = state->inode;
>  	struct nfs_inode *nfsi = NFS_I(inode);
>  	struct file_lock *fl;
> +	struct nfs4_lock_state *lsp;
>  	int status = 0;
>  	struct file_lock_context *flctx = inode->i_flctx;
>  	struct list_head *list;
> @@ -1522,7 +1523,9 @@ static int nfs4_reclaim_locks(struct nfs4_state *state, const struct nfs4_state_
>  		case -NFS4ERR_DENIED:
>  		case -NFS4ERR_RECLAIM_BAD:
>  		case -NFS4ERR_RECLAIM_CONFLICT:
> -			/* kill_proc(fl->fl_pid, SIGLOST, 1); */
> +			lsp = fl->fl_u.nfs4_fl.owner;
> +			if (lsp)
> +				set_bit(NFS_LOCK_LOST, &lsp->ls_flags);
>  			status = 0;
>  		}
>  		spin_lock(&flctx->flc_lock);
> -- 
> 2.14.0.rc0.dirty

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-12-19 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 22:57 [PATCH] NFSv4: always set NFS_LOCK_LOST when a lock is lost NeilBrown
2017-12-19 21:15 ` NeilBrown [this message]
2018-02-01 16:23   ` Olga Kornievskaia
2018-02-01 17:51     ` Olga Kornievskaia
2018-02-01 22:04       ` NeilBrown

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=87bmiul8r6.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=Anna.Schumaker@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;
as well as URLs for NNTP newsgroup(s).