public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Dai Ngo <dai.ngo@oracle.com>, chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org, linux-nfs@stwm.de
Subject: Re: [PATCH 1/3] SUNRPC: remove printk when back channel request not found
Date: Fri, 15 Dec 2023 14:37:32 -0500	[thread overview]
Message-ID: <824fdbfe883c348c9829407ef2bd4f1e0b77d34d.camel@kernel.org> (raw)
In-Reply-To: <1702667703-17978-2-git-send-email-dai.ngo@oracle.com>

On Fri, 2023-12-15 at 11:15 -0800, Dai Ngo wrote:
> If the client interface is down, or there is a network partition between
> the client and server, that prevents the callback request to reach the
> client TCP on the server will keep re-transmitting the callback for about
> ~9 minutes before giving up and closes the connection.
> 
> If the connection between the client and the server is re-established
> before the connection is closed and after the callback timed out (9 secs)
> then the re-transmitted callback request will arrive at the client. When
> the server receives the reply of the callback, receive_cb_reply prints the
> "Got unrecognized reply..." message in the system log since the callback
> request was already removed from the server xprt's recv_queue.
> 
> Even though this scenario has no effect on the server operation, a
> malicious client can take advantage of this behavior and send thousand
> of callback replies with random XIDs to fill up the server's system log.
> 
> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> ---
>  net/sunrpc/svcsock.c | 8 +-------
>  1 file changed, 1 insertion(+), 7 deletions(-)
> 
> diff --git a/net/sunrpc/svcsock.c b/net/sunrpc/svcsock.c
> index 998687421fa6..3e89dc0afbef 100644
> --- a/net/sunrpc/svcsock.c
> +++ b/net/sunrpc/svcsock.c
> @@ -1060,7 +1060,7 @@ static int receive_cb_reply(struct svc_sock *svsk, struct svc_rqst *rqstp)
>  	spin_lock(&bc_xprt->queue_lock);
>  	req = xprt_lookup_rqst(bc_xprt, xid);
>  	if (!req)
> -		goto unlock_notfound;
> +		goto unlock_eagain;
>  
>  	memcpy(&req->rq_private_buf, &req->rq_rcv_buf, sizeof(struct xdr_buf));
>  	/*
> @@ -1077,12 +1077,6 @@ static int receive_cb_reply(struct svc_sock *svsk, struct svc_rqst *rqstp)
>  	rqstp->rq_arg.len = 0;
>  	spin_unlock(&bc_xprt->queue_lock);
>  	return 0;
> -unlock_notfound:
> -	printk(KERN_NOTICE
> -		"%s: Got unrecognized reply: "
> -		"calldir 0x%x xpt_bc_xprt %p xid %08x\n",
> -		__func__, ntohl(calldir),
> -		bc_xprt, ntohl(xid));
>  unlock_eagain:
>  	spin_unlock(&bc_xprt->queue_lock);
>  	return -EAGAIN;

Makes sense. It's a cryptic error message for most admins.

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

  reply	other threads:[~2023-12-15 19:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 19:15 [PATCH 0/3] Bug fixes for NFSD callback Dai Ngo
2023-12-15 19:15 ` [PATCH 1/3] SUNRPC: remove printk when back channel request not found Dai Ngo
2023-12-15 19:37   ` Jeff Layton [this message]
2023-12-15 19:15 ` [PATCH 2/3] NFSD: restore delegation's sc_count if nfsd4_run_cb fails Dai Ngo
2023-12-15 19:42   ` Jeff Layton
2023-12-15 20:00     ` dai.ngo
2023-12-15 20:15       ` Jeff Layton
2023-12-15 20:22         ` dai.ngo
2023-12-15 19:15 ` [PATCH 3/3] NFSD: Fix server reboot hang problem when callback workqueue is stuck Dai Ngo
2023-12-15 19:54   ` Chuck Lever
2023-12-15 20:40     ` dai.ngo
2023-12-15 21:41       ` Chuck Lever
2023-12-15 21:55         ` dai.ngo
2023-12-16  1:21           ` Chuck Lever
2023-12-16  3:18             ` dai.ngo
2023-12-16  3:57               ` Chuck Lever
2023-12-16 22:44                 ` dai.ngo
2023-12-18 16:02                   ` Chuck Lever
2023-12-18 18:17                     ` dai.ngo
2023-12-18 19:10                       ` Chuck Lever
2023-12-18 20:27                         ` dai.ngo
2023-12-15 19:54   ` Jeff Layton
2023-12-15 20:18     ` dai.ngo
2023-12-15 20:25       ` Jeff Layton

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=824fdbfe883c348c9829407ef2bd4f1e0b77d34d.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=linux-nfs@stwm.de \
    --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