public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Robert Szentmihalyi <robert.szentmihalyi@gmx.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Group limit for NFS exported file systems
Date: Wed, 23 Aug 2006 11:36:09 -0400	[thread overview]
Message-ID: <44EC75E9.2020608@redhat.com> (raw)
In-Reply-To: <p73u043656n.fsf@verdi.suse.de>

Andi Kleen wrote:
> "Robert Szentmihalyi" <robert.szentmihalyi@gmx.de> writes:
>
>   
>> is there a group limit for NFS exported file systems in recent kernels?
>> One if my users cannot access directories that belong to a group he actually _is_ a member of. That, however, is true only when accessing them over NFS. On the local file system, everything is fine. UIDs and GIDs are the same on client and server, so that cannot be the problem. Client and server run Gentoo Linux with kernel 2.6.16 on the server and 2.6.17 on the client.
>>     
>
> NFSv2 has a 8 groups limit in the protocol iirc.

Ahh, no.  None of the NFS protocols define anything about the authentication
protocols.  This is defined by the RPC protocol and it defines a limit of 16
for AUTH_SYS, otherwise known as AUTH_UNIX.

Interestingly, the original NFSv2 implementations had a limit of 8, then 10,
and then finally 16.

    Thanx...

       ps

      parent reply	other threads:[~2006-08-23 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  9:16 Group limit for NFS exported file systems Robert Szentmihalyi
2006-08-23  9:32 ` Jan Engelhardt
2006-08-23  9:43   ` Robert Szentmihalyi
2006-08-23 10:55 ` Ray Lee
2006-08-23 11:11   ` Robert Szentmihalyi
2006-08-23 11:35     ` Ray Lee
2006-08-23 11:57       ` Jan Engelhardt
2006-08-23 13:01         ` Ray Lee
2006-08-23 14:20     ` Peter Staubach
2006-08-23 11:51 ` Andi Kleen
2006-08-23 14:13   ` Trond Myklebust
2006-08-23 15:36   ` Peter Staubach [this message]

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=44EC75E9.2020608@redhat.com \
    --to=staubach@redhat.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.szentmihalyi@gmx.de \
    /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