From: Chuck Lever <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
"J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 7/7] nfsd: lift NFSv4.0 handling out of nfsd4_cb_sequence_done()
Date: Sat, 8 Feb 2025 12:05:23 -0500 [thread overview]
Message-ID: <0eabc5b5-88ca-4d48-a5de-80a7be03a1f6@oracle.com> (raw)
In-Reply-To: <20250207-nfsd-6-14-v5-7-f3b54fb60dc0@kernel.org>
On 2/7/25 4:53 PM, Jeff Layton wrote:
> It's a bit strange to call nfsd4_cb_sequence_done() on a callback with no
> CB_SEQUENCE. Lift the handling of restarting a call into a new helper,
> and move the handling of NFSv4.0 into nfsd4_cb_done().
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> fs/nfsd/nfs4callback.c | 53 ++++++++++++++++++++++++++------------------------
> 1 file changed, 28 insertions(+), 25 deletions(-)
>
> diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> index d6e3e8bb2efabadda9f922318880e12e1cb2c23f..a4427e2f6182415755b646dba1a1ef4acddc0709 100644
> --- a/fs/nfsd/nfs4callback.c
> +++ b/fs/nfsd/nfs4callback.c
> @@ -1328,28 +1328,23 @@ static void nfsd4_cb_prepare(struct rpc_task *task, void *calldata)
> rpc_call_start(task);
> }
>
> -/* Returns true if CB_COMPOUND processing should continue */
> -static bool nfsd4_cb_sequence_done(struct rpc_task *task, struct nfsd4_callback *cb)
> +static void requeue_callback(struct rpc_task *task, struct nfsd4_callback *cb)
Nit: requeue_callback => nfsd4_requeue_cb().
Once the nfsd41_cb_release_slot() call is gone from this helper, it
can easily be placed just after nfsd4_queue_cb(), which seems like
more legible code organization.
Just small nits this time. v6 ought to be ready for me to pull.
> {
> struct nfs4_client *clp = cb->cb_clp;
> - struct nfsd4_session *session = clp->cl_cb_session;
> - bool ret = false;
> -
> - if (!clp->cl_minorversion) {
> - /*
> - * If the backchannel connection was shut down while this
> - * task was queued, we need to resubmit it after setting up
> - * a new backchannel connection.
> - *
> - * Note that if we lost our callback connection permanently
> - * the submission code will error out, so we don't need to
> - * handle that case here.
> - */
> - if (RPC_SIGNALLED(task))
> - goto requeue;
>
> - return true;
> + nfsd41_cb_release_slot(cb);
> + if (!test_bit(NFSD4_CLIENT_CB_KILL, &clp->cl_flags)) {
> + trace_nfsd_cb_restart(clp, cb);
> + task->tk_status = 0;
> + cb->cb_need_restart = true;
> }
> +}
> +
> +/* Returns true if CB_COMPOUND processing should continue */
> +static bool nfsd4_cb_sequence_done(struct rpc_task *task, struct nfsd4_callback *cb)
> +{
> + struct nfsd4_session *session = cb->cb_clp->cl_cb_session;
> + bool ret = false;
>
> if (cb->cb_held_slot < 0)
> goto requeue;
> @@ -1429,12 +1424,7 @@ static bool nfsd4_cb_sequence_done(struct rpc_task *task, struct nfsd4_callback
> return false;
> }
> requeue:
> - nfsd41_cb_release_slot(cb);
> - if (!test_bit(NFSD4_CLIENT_CB_KILL, &clp->cl_flags)) {
> - trace_nfsd_cb_restart(clp, cb);
> - task->tk_status = 0;
> - cb->cb_need_restart = true;
> - }
> + requeue_callback(task, cb);
> return false;
> }
>
> @@ -1445,8 +1435,21 @@ static void nfsd4_cb_done(struct rpc_task *task, void *calldata)
>
> trace_nfsd_cb_rpc_done(clp);
>
> - if (!nfsd4_cb_sequence_done(task, cb))
> + if (!clp->cl_minorversion) {
> + /*
> + * If the backchannel connection was shut down while this
> + * task was queued, we need to resubmit it after setting up
> + * a new backchannel connection.
> + *
> + * Note that if we lost our callback connection permanently
> + * the submission code will error out, so we don't need to
> + * handle that case here.
> + */
> + if (RPC_SIGNALLED(task))
> + requeue_callback(task, cb);
> + } else if (!nfsd4_cb_sequence_done(task, cb)) {
> return;
> + }
>
> if (cb->cb_status) {
> WARN_ONCE(task->tk_status,
>
--
Chuck Lever
prev parent reply other threads:[~2025-02-08 17:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 21:53 [PATCH v5 0/7] nfsd: CB_SEQUENCE error handling fixes and cleanups Jeff Layton
2025-02-07 21:53 ` [PATCH v5 1/7] nfsd: prepare nfsd4_cb_sequence_done() for error handling rework Jeff Layton
2025-02-07 21:53 ` [PATCH v5 2/7] nfsd: always release slot when requeueing callback Jeff Layton
2025-02-08 16:57 ` Chuck Lever
2025-02-08 17:55 ` Jeff Layton
2025-02-07 21:53 ` [PATCH v5 3/7] nfsd: only check RPC_SIGNALLED() when restarting rpc_task Jeff Layton
2025-02-08 16:59 ` Chuck Lever
2025-02-07 21:53 ` [PATCH v5 4/7] nfsd: when CB_SEQUENCE gets ESERVERFAULT don't increment seq_nr Jeff Layton
2025-02-08 17:13 ` Chuck Lever
2025-02-07 21:53 ` [PATCH v5 5/7] nfsd: handle CB_SEQUENCE NFS4ERR_BADSLOT better Jeff Layton
2025-02-07 21:53 ` [PATCH v5 6/7] nfsd: handle CB_SEQUENCE NFS4ERR_SEQ_MISORDERED error better Jeff Layton
2025-02-08 17:01 ` Chuck Lever
2025-02-08 18:02 ` Jeff Layton
2025-02-08 18:40 ` Tom Talpey
2025-02-08 19:08 ` Jeff Layton
2025-02-08 19:18 ` Tom Talpey
2025-02-08 20:45 ` Jeff Layton
2025-02-08 21:07 ` Chuck Lever
2025-02-09 1:24 ` Tom Talpey
2025-02-09 2:14 ` Jeff Layton
2025-02-09 16:26 ` Tom Talpey
2025-02-09 16:51 ` Jeff Layton
2025-02-09 16:58 ` Tom Talpey
2025-02-09 17:05 ` Jeff Layton
2025-02-09 18:52 ` Tom Talpey
2025-02-07 21:53 ` [PATCH v5 7/7] nfsd: lift NFSv4.0 handling out of nfsd4_cb_sequence_done() Jeff Layton
2025-02-08 17:05 ` Chuck Lever [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=0eabc5b5-88ca-4d48-a5de-80a7be03a1f6@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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