public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Roberto Bergantinos Corpas <rbergant@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] sunrpc: raise kernel RPC channel buffer size
Date: Mon, 19 Oct 2020 09:20:00 -0400	[thread overview]
Message-ID: <20201019132000.GA32403@fieldses.org> (raw)
In-Reply-To: <20201019093356.7395-1-rbergant@redhat.com>

On Mon, Oct 19, 2020 at 11:33:56AM +0200, Roberto Bergantinos Corpas wrote:
> Its possible that using AUTH_SYS and mountd manage-gids option a
> user may hit the 8k RPC channel buffer limit. This have been observed
> on field, causing unanswered RPCs on clients after mountd fails to
> write on channel :
> 
> rpc.mountd[11231]: auth_unix_gid: error writing reply
> 
> Userland nfs-utils uses a buffer size of 32k (RPC_CHAN_BUF_SIZE), so
> lets match those two.

Thanks, applying.

That should allow about 4000 group memberships.  If that doesn't do it
then maybe it's time to rethink....

--b.

> 
> Signed-off-by: Roberto Bergantinos Corpas <rbergant@redhat.com>
> ---
>  net/sunrpc/cache.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/sunrpc/cache.c b/net/sunrpc/cache.c
> index baef5ee43dbb..08df4c599ab3 100644
> --- a/net/sunrpc/cache.c
> +++ b/net/sunrpc/cache.c
> @@ -908,7 +908,7 @@ static ssize_t cache_do_downcall(char *kaddr, const char __user *buf,
>  static ssize_t cache_slow_downcall(const char __user *buf,
>  				   size_t count, struct cache_detail *cd)
>  {
> -	static char write_buf[8192]; /* protected by queue_io_mutex */
> +	static char write_buf[32768]; /* protected by queue_io_mutex */
>  	ssize_t ret = -EINVAL;
>  
>  	if (count >= sizeof(write_buf))
> -- 
> 2.21.0

  reply	other threads:[~2020-10-19 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  9:33 [PATCH] sunrpc: raise kernel RPC channel buffer size Roberto Bergantinos Corpas
2020-10-19 13:20 ` J. Bruce Fields [this message]
2020-10-23  9:44   ` Geert Uytterhoeven
2020-10-24  0:04     ` J. Bruce Fields
2020-10-24  1:29       ` Roberto Bergantinos Corpas
2020-10-24  2:09         ` 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=20201019132000.GA32403@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rbergant@redhat.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