Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH nfsd-next] nfsd: fix uninitialised slot info when a request is retried
Date: Tue, 28 Jan 2025 06:16:41 -0500	[thread overview]
Message-ID: <0f3b3f8dca6bfd111aceae6c132e645a537f3209.camel@kernel.org> (raw)
In-Reply-To: <173801910367.22054.5749156945763150749@noble.neil.brown.name>

On Tue, 2025-01-28 at 10:05 +1100, NeilBrown wrote:
> A recent patch moved the assignment of seq->maxslots from before the
> test for a resent request (which ends with a goto) to after, resulting
> in it not being run in that case.  This results in the server returning
> bogus "high slot id" and "target high slot id" values.
> 
> The assignments to ->maxslots and ->target_maxslots need to be *after*
> the out: label so that the correct values are returned in replies to
> requests that are served from cache.
> 
> Fixes: 60aa6564317d ("nfsd: allocate new session-based DRC slots on demand.")
> Signed-off-by: NeilBrown <neilb@suse.de>
> ---
> 
> Feel free to squash this into the offending patch, though subsequent
> patches will need to be refreshed carefully.  Or just add it as-is.
> Thanks.
> 
>  fs/nfsd/nfs4state.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index cc819b8e8acd..b42e2ab7a042 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -4460,10 +4460,11 @@ nfsd4_sequence(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>  			}
>  		} while (slot && --cnt > 0);
>  	}
> +
> +out:
>  	seq->maxslots = max(session->se_target_maxslots, seq->maxslots);
>  	seq->target_maxslots = session->se_target_maxslots;
>  
> -out:
>  	switch (clp->cl_cb_state) {
>  	case NFSD4_CB_DOWN:
>  		seq->status_flags = SEQ4_STATUS_CB_PATH_DOWN;
> 
> base-commit: c1d6e5f7635895b5e9b2e4a9e4b7cdb9cc07eaf7

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-01-28 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 23:05 [PATCH nfsd-next] nfsd: fix uninitialised slot info when a request is retried NeilBrown
2025-01-28 11:16 ` Jeff Layton [this message]
2025-01-28 14:40 ` cel

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=0f3b3f8dca6bfd111aceae6c132e645a537f3209.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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