Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] Revert "NFSD: Force all NFSv4.2 COPY requests to be synchronous"
Date: Wed, 18 Jun 2025 09:02:22 -0400	[thread overview]
Message-ID: <54f9237dc5a5f9422c2fcdf1251b4e06230aa6ed.camel@kernel.org> (raw)
In-Reply-To: <20250618125803.1131150-1-cel@kernel.org>

On Wed, 2025-06-18 at 08:58 -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> In the past several kernel releases, we've made NFSv4.2 async copy
> reliable:
>  - The Linux NFS client and server now both implement and use the
>    NFSv4.2 OFFLOAD_STATUS operation
>  - The Linux NFS server keeps copy stateids around longer
>  - The Linux NFS client and server now both implement referring call
>    lists
> 
> And resilient against DoS:
>  - The Linux NFS server limits the number of concurrent async copy
>    operations
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  fs/nfsd/nfs4proc.c | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index f13abbb13b38..2b76a8267a4b 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -1917,13 +1917,6 @@ nfsd4_copy(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>  	struct nfsd42_write_res *result;
>  	__be32 status;
>  
> -	/*
> -	 * Currently, async COPY is not reliable. Force all COPY
> -	 * requests to be synchronous to avoid client application
> -	 * hangs waiting for COPY completion.
> -	 */
> -	nfsd4_copy_set_sync(copy, true);
> -
>  	result = &copy->cp_res;
>  	nfsd_copy_write_verifier((__be32 *)&result->wr_verifier.data, nn);
>  

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

  reply	other threads:[~2025-06-18 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 12:58 [RFC PATCH] Revert "NFSD: Force all NFSv4.2 COPY requests to be synchronous" Chuck Lever
2025-06-18 13:02 ` Jeff Layton [this message]
2025-06-18 19:22 ` Aurélien Couderc
2025-07-12 13:06   ` Aurélien Couderc
2025-07-13 17:50     ` Chuck Lever
2025-07-14 10:36       ` Aurélien Couderc
2025-07-14 10:38         ` Aurélien Couderc
2025-07-14 13:59         ` Chuck Lever

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=54f9237dc5a5f9422c2fcdf1251b4e06230aa6ed.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --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