* [PATCH 1/1] NFSv4.1: handle NFS4ERR_NOSPC by CREATE_SESSION
@ 2021-11-15 20:18 Olga Kornievskaia
2021-11-15 20:34 ` Trond Myklebust
0 siblings, 1 reply; 2+ messages in thread
From: Olga Kornievskaia @ 2021-11-15 20:18 UTC (permalink / raw)
To: trond.myklebust, anna.schumaker; +Cc: linux-nfs
From: Olga Kornievskaia <kolga@netapp.com>
When the client receives ERR_NOSPC on reply to CREATE_SESSION
it leads to a client hanging in nfs_wait_client_init_complete().
Instead, complete and fail the client initiation with an EIO
error which allows for the mount command to fail instead of
hanging.
Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
---
fs/nfs/nfs4state.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
index ecc4594299d6..50fa963665ba 100644
--- a/fs/nfs/nfs4state.c
+++ b/fs/nfs/nfs4state.c
@@ -1998,6 +1998,10 @@ static int nfs4_handle_reclaim_lease_error(struct nfs_client *clp, int status)
dprintk("%s: exit with error %d for server %s\n",
__func__, -EPROTONOSUPPORT, clp->cl_hostname);
return -EPROTONOSUPPORT;
+ case -NFS4ERR_NOSPC:
+ if (clp->cl_cons_state == NFS_CS_SESSION_INITING)
+ nfs_mark_client_ready(clp, -EIO);
+ return -EIO;
case -NFS4ERR_NOT_SAME: /* FixMe: implement recovery
* in nfs4_exchange_id */
default:
--
2.27.0
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH 1/1] NFSv4.1: handle NFS4ERR_NOSPC by CREATE_SESSION
2021-11-15 20:18 [PATCH 1/1] NFSv4.1: handle NFS4ERR_NOSPC by CREATE_SESSION Olga Kornievskaia
@ 2021-11-15 20:34 ` Trond Myklebust
0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2021-11-15 20:34 UTC (permalink / raw)
To: anna.schumaker@netapp.com, olga.kornievskaia@gmail.com
Cc: linux-nfs@vger.kernel.org
On Mon, 2021-11-15 at 15:18 -0500, Olga Kornievskaia wrote:
> From: Olga Kornievskaia <kolga@netapp.com>
>
> When the client receives ERR_NOSPC on reply to CREATE_SESSION
> it leads to a client hanging in nfs_wait_client_init_complete().
> Instead, complete and fail the client initiation with an EIO
> error which allows for the mount command to fail instead of
> hanging.
>
> Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
> ---
> fs/nfs/nfs4state.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index ecc4594299d6..50fa963665ba 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -1998,6 +1998,10 @@ static int
> nfs4_handle_reclaim_lease_error(struct nfs_client *clp, int status)
> dprintk("%s: exit with error %d for server %s\n",
> __func__, -EPROTONOSUPPORT, clp-
> >cl_hostname);
> return -EPROTONOSUPPORT;
> + case -NFS4ERR_NOSPC:
Shouldn't this be 'case -ENOSPC:'?
> + if (clp->cl_cons_state == NFS_CS_SESSION_INITING)
> + nfs_mark_client_ready(clp, -EIO);
> + return -EIO;
> case -NFS4ERR_NOT_SAME: /* FixMe: implement recovery
> * in nfs4_exchange_id */
> default:
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-11-15 20:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-11-15 20:18 [PATCH 1/1] NFSv4.1: handle NFS4ERR_NOSPC by CREATE_SESSION Olga Kornievskaia
2021-11-15 20:34 ` Trond Myklebust
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox