From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Dai Ngo <dai.ngo@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN
Date: Thu, 16 Sep 2021 15:55:46 -0400 [thread overview]
Message-ID: <20210916195546.GA32690@fieldses.org> (raw)
In-Reply-To: <8EB546E2-124E-4FB5-B72B-15E0CB66798F@oracle.com>
On Thu, Sep 16, 2021 at 07:00:20PM +0000, Chuck Lever III wrote:
> Bruce, Dai -
>
> > On Sep 16, 2021, at 2:22 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
> >
> > When the back channel enters SEQ4_STATUS_CB_PATH_DOWN state, the client
> > recovers by sending BIND_CONN_TO_SESSION but the server fails to recover
> > the back channel and leaves it as NFSD4_CB_DOWN.
> >
> > Fix by enhancing nfsd4_bind_conn_to_session to probe the back channel
> > by calling nfsd4_probe_callback.
> >
> > Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
>
> I'm wondering if this one is appropriate to pull into v5.15-rc.
I think so.
Dai, do you have a pynfs test for this case?
--b.
> > ---
> > fs/nfsd/nfs4state.c | 16 +++++++++++++---
> > 1 file changed, 13 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> > index 54e5317f00f1..63b4d0e6fc29 100644
> > --- a/fs/nfsd/nfs4state.c
> > +++ b/fs/nfsd/nfs4state.c
> > @@ -3580,7 +3580,7 @@ static struct nfsd4_conn *__nfsd4_find_conn(struct svc_xprt *xpt, struct nfsd4_s
> > }
> >
> > static __be32 nfsd4_match_existing_connection(struct svc_rqst *rqst,
> > - struct nfsd4_session *session, u32 req)
> > + struct nfsd4_session *session, u32 req, struct nfsd4_conn **conn)
> > {
> > struct nfs4_client *clp = session->se_client;
> > struct svc_xprt *xpt = rqst->rq_xprt;
> > @@ -3603,6 +3603,8 @@ static __be32 nfsd4_match_existing_connection(struct svc_rqst *rqst,
> > else
> > status = nfserr_inval;
> > spin_unlock(&clp->cl_lock);
> > + if (status == nfs_ok && conn)
> > + *conn = c;
> > return status;
> > }
> >
> > @@ -3627,8 +3629,16 @@ __be32 nfsd4_bind_conn_to_session(struct svc_rqst *rqstp,
> > status = nfserr_wrong_cred;
> > if (!nfsd4_mach_creds_match(session->se_client, rqstp))
> > goto out;
> > - status = nfsd4_match_existing_connection(rqstp, session, bcts->dir);
> > - if (status == nfs_ok || status == nfserr_inval)
> > + status = nfsd4_match_existing_connection(rqstp, session,
> > + bcts->dir, &conn);
> > + if (status == nfs_ok) {
> > + if (bcts->dir == NFS4_CDFC4_FORE_OR_BOTH ||
> > + bcts->dir == NFS4_CDFC4_BACK)
> > + conn->cn_flags |= NFS4_CDFC4_BACK;
> > + nfsd4_probe_callback(session->se_client);
> > + goto out;
> > + }
> > + if (status == nfserr_inval)
> > goto out;
> > status = nfsd4_map_bcts_dir(&bcts->dir);
> > if (status)
> > --
> > 2.9.5
> >
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2021-09-16 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 18:22 [PATCH RFC v3 0/2] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2021-09-16 18:22 ` [PATCH v3 1/3] fs/lock: add new callback, lm_expire_lock, to lock_manager_operations Dai Ngo
2021-09-16 18:22 ` [PATCH v3 2/3] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2021-09-22 21:14 ` J. Bruce Fields
2021-09-22 22:16 ` dai.ngo
2021-09-23 1:18 ` J. Bruce Fields
2021-09-23 17:09 ` dai.ngo
2021-09-23 1:34 ` J. Bruce Fields
2021-09-23 17:09 ` dai.ngo
2021-09-23 19:32 ` J. Bruce Fields
2021-09-24 20:53 ` dai.ngo
2021-09-16 18:22 ` [PATCH v3 3/3] nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN Dai Ngo
2021-09-16 19:00 ` Chuck Lever III
2021-09-16 19:55 ` Bruce Fields [this message]
2021-09-16 20:15 ` dai.ngo
2021-09-17 18:23 ` dai.ngo
2021-09-23 1:47 ` [PATCH RFC v3 0/2] nfsd: Initial implementation of NFSv4 Courteous Server J. Bruce Fields
2021-09-23 17:15 ` dai.ngo
2021-09-23 19:37 ` dai.ngo
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=20210916195546.GA32690@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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).