linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 02/10] svcauth_gss: Close connection when dropping an incoming message
Date: Fri, 2 Dec 2016 22:17:32 -0500	[thread overview]
Message-ID: <20161203031732.GA21785@fieldses.org> (raw)
In-Reply-To: <20161129160434.4477.76542.stgit@klimt.1015granger.net>

By the way, pynfs test GSS1 now fails with a complaint about the dropped
connection.

I'll fix it up to require the dropped connection, since we now think
it's actually a bug to do otherwise.

--b.

On Tue, Nov 29, 2016 at 11:04:34AM -0500, Chuck Lever wrote:
> S5.3.3.1 of RFC 2203 requires that an incoming GSS-wrapped message
> whose sequence number lies outside the current window is dropped.
> The rationale is:
> 
>   The reason for discarding requests silently is that the server
>   is unable to determine if the duplicate or out of range request
>   was due to a sequencing problem in the client, network, or the
>   operating system, or due to some quirk in routing, or a replay
>   attack by an intruder.  Discarding the request allows the client
>   to recover after timing out, if indeed the duplication was
>   unintentional or well intended.
> 
> However, clients may rely on the server dropping the connection to
> indicate that a retransmit is needed. Without a connection reset, a
> client can wait forever without retransmitting, and the workload
> just stops dead. I've reproduced this behavior by running xfstests
> generic/323 on an NFSv4.0 mount with proto=rdma and sec=krb5i.
> 
> To address this issue, have the server close the connection when it
> silently discards an incoming message due to a GSS sequence number
> problem.
> 
> There are a few other places where the server will never reply.
> Change those spots in a similar fashion.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  net/sunrpc/auth_gss/svcauth_gss.c |    2 +-
>  net/sunrpc/svc.c                  |   14 +++++++++-----
>  2 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/net/sunrpc/auth_gss/svcauth_gss.c b/net/sunrpc/auth_gss/svcauth_gss.c
> index 45662d7..886e9d38 100644
> --- a/net/sunrpc/auth_gss/svcauth_gss.c
> +++ b/net/sunrpc/auth_gss/svcauth_gss.c
> @@ -1548,7 +1548,7 @@ static void destroy_use_gss_proxy_proc_entry(struct net *net) {}
>  	ret = SVC_COMPLETE;
>  	goto out;
>  drop:
> -	ret = SVC_DROP;
> +	ret = SVC_CLOSE;
>  out:
>  	if (rsci)
>  		cache_put(&rsci->h, sn->rsc_cache);
> diff --git a/net/sunrpc/svc.c b/net/sunrpc/svc.c
> index 7c8070e..75f290b 100644
> --- a/net/sunrpc/svc.c
> +++ b/net/sunrpc/svc.c
> @@ -1155,8 +1155,7 @@ static __printf(2,3) void svc_printk(struct svc_rqst *rqstp, const char *fmt, ..
>  	case SVC_DENIED:
>  		goto err_bad_auth;
>  	case SVC_CLOSE:
> -		if (test_bit(XPT_TEMP, &rqstp->rq_xprt->xpt_flags))
> -			svc_close_xprt(rqstp->rq_xprt);
> +		goto close;
>  	case SVC_DROP:
>  		goto dropit;
>  	case SVC_COMPLETE:
> @@ -1246,7 +1245,7 @@ static __printf(2,3) void svc_printk(struct svc_rqst *rqstp, const char *fmt, ..
>  
>   sendit:
>  	if (svc_authorise(rqstp))
> -		goto dropit;
> +		goto close;
>  	return 1;		/* Caller can now send it */
>  
>   dropit:
> @@ -1254,11 +1253,16 @@ static __printf(2,3) void svc_printk(struct svc_rqst *rqstp, const char *fmt, ..
>  	dprintk("svc: svc_process dropit\n");
>  	return 0;
>  
> + close:
> +	if (test_bit(XPT_TEMP, &rqstp->rq_xprt->xpt_flags))
> +		svc_close_xprt(rqstp->rq_xprt);
> +	dprintk("svc: svc_process close\n");
> +	return 0;
> +
>  err_short_len:
>  	svc_printk(rqstp, "short len %Zd, dropping request\n",
>  			argv->iov_len);
> -
> -	goto dropit;			/* drop request */
> +	goto close;
>  
>  err_bad_rpc:
>  	serv->sv_stats->rpcbadfmt++;

  reply	other threads:[~2016-12-03  3:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 16:04 [PATCH v3 00/10] Server-side NFS/RDMA patches proposed for v4.10 Chuck Lever
2016-11-29 16:04 ` [PATCH v3 01/10] svcrdma: Clear xpt_bc_xps in xprt_setup_rdma_bc() error exit arm Chuck Lever
2016-11-29 16:04 ` [PATCH v3 02/10] svcauth_gss: Close connection when dropping an incoming message Chuck Lever
2016-12-03  3:17   ` J. Bruce Fields [this message]
2016-11-29 16:04 ` [PATCH v3 03/10] svcrdma: Renovate sendto chunk list parsing Chuck Lever
2016-11-29 16:04 ` [PATCH v3 04/10] svcrdma: Remove BH-disabled spin locking in svc_rdma_send() Chuck Lever
2016-11-29 16:04 ` [PATCH v3 05/10] svcrdma: Remove DMA map accounting Chuck Lever
2016-11-29 16:05 ` [PATCH v3 06/10] svcrdma: Remove svc_rdma_op_ctxt::wc_status Chuck Lever
2016-11-29 16:05 ` [PATCH v3 07/10] svcrdma: Remove unused variables in xprt_rdma_bc_allocate() Chuck Lever
2016-11-29 16:05 ` [PATCH v3 08/10] svcrdma: Remove unused variable in rdma_copy_tail() Chuck Lever
2016-11-29 16:05 ` [PATCH v3 09/10] svcrdma: Break up dprintk format in svc_rdma_accept() Chuck Lever
2016-11-29 16:05 ` [PATCH v3 10/10] svcrdma: Further clean-up of svc_rdma_get_inv_rkey() Chuck Lever
2016-11-30 22:30 ` [PATCH v3 00/10] Server-side NFS/RDMA patches proposed for v4.10 J. Bruce Fields

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=20161203031732.GA21785@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@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).