All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Assarsson, Emil" <Emil.Assarsson@sonyericsson.com>
Cc: "'linux-nfs@vger.kernel.org'" <linux-nfs@vger.kernel.org>
Subject: Re: mountd --manage-gids supports max 100 groups?
Date: Thu, 10 Mar 2011 07:35:15 +1100	[thread overview]
Message-ID: <20110310073515.799d1530@notabene.brown> (raw)
In-Reply-To: <2BF070A7A2375D46BA1B6087F8D5DCB678B8E772B8@seldmbx01.corpusers.net>

On Wed, 9 Mar 2011 16:20:42 +0100 "Assarsson, Emil"
<Emil.Assarsson@sonyericsson.com> wrote:

> Hi All,
> 
> Running linux kernel 2.6.32 and nfs-utils 1.2.0 (Ubuntu Lucid)
> 
> A regular user in our company usually is member of more than 300 groups. Some user even have up to 600. We want to use the --manage-gids option for mountd. However it seems to me that it is limited to about 100 groups.
> 
> The reason seems to be that there is a hard limit for mountd but also that the /proc/net/rpc/auth.unix.gid/channel won't accept more than 1008 characters as input.
> 
> I tried to adjust the code for mountd so that it tried to add up to 1000 groups but then I ran in to the channel problem.
> 
> Can someone please guide me to the place where I can adjust this limit?
> 

The limit should be 8192, not 1008.

This is set in net/sunrpc/cache.c
If the write is less than one page, it is handled in cache_downcall().
If it is bigger it is passed to cache_slow_downcall() which stops at
8192 (but could trivially be make to handle more).

What is your evidence that '.../channel won't accept more than 1008
characters as input" ???

Thanks,
NeilBrown

  reply	other threads:[~2011-03-09 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 15:20 mountd --manage-gids supports max 100 groups? Assarsson, Emil
2011-03-09 20:35 ` NeilBrown [this message]
2011-03-10  9:39   ` Assarsson, Emil
2011-03-10 10:28     ` NeilBrown

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=20110310073515.799d1530@notabene.brown \
    --to=neilb@suse.de \
    --cc=Emil.Assarsson@sonyericsson.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.