From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Groups beyond 32
Date: 17 Jul 2002 16:36:35 -0700 [thread overview]
Message-ID: <ah4v23$39o$1@cesium.transmeta.com> (raw)
In-Reply-To: 1026936556.25347.48.camel@UberGeek
Followup to: <1026936556.25347.48.camel@UberGeek>
By author: Austin Gonyou <austin@digitalroadkill.net>
In newsgroup: linux.dev.kernel
>
> The problem now is more one of maintenance. Most distributions do not
> support groups > 32 AFAIK. So, it's lead me to ask the following
> questions:
>
> 1. Why, in general, is the limit so low?
> For specific application, mainly auditing and such, this would be
> advantageous I think.
>
Mostly to cap the amount of storage to maintain in kernel space, and
for historical reasons.
> 2. What is required to limit the dependence on groups to just GLIBC or
> just the kernel? Is that even possible?
The main problem is programs who do things like:
gid_t mygroups[NGROUPS];
Other than that, it should all be in kernel space. According to
POSIX, the NGROUPS above really should be sysconf(_SC_NGROUPS_MAX) --
NGROUPS_MAX is defined as a *guaranteed minimum* of
sysconf(_SC_NGROUPS_MAX). Obviously there needs to be a kernel ->
libc interface for the sysconf.
FWIW, POSIX specifies:
Application writers should note that {NGROUPS_MAX} is not
necessarily a constant on all implementations.
(glibc has #define NGROUPS NGROUPS_MAX).
> 3. Is there any true advantage to supporting more than 32 groups, or
> creating "meta-groups" to get around the problem?
There probably is.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-07-17 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 20:09 [RFC] Groups beyond 32 Austin Gonyou
2002-07-17 23:36 ` H. Peter Anvin [this message]
2002-07-17 23:42 ` Tim Hockin
2002-07-18 5:07 ` Austin Gonyou
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 14:57 Jesse Pollard
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='ah4v23$39o$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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