kern.ngroups (non) setting ... new bounty ?
Pawel Jakub Dawidek
pjd at FreeBSD.org
Thu Sep 27 04:10:44 PDT 2007
On Tue, Sep 25, 2007 at 09:51:06AM -0700, rsync.net wrote:
> It has been impossible to change kern.ngroups - at least for several years
> now. It was not fixed in either 5.x or 6.x :
> It is seemingly a difficult problem:
> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html 
> However it should be solved - we can't be the only ones out there trying
> to add a UID to more than 16 groups...
> The rsync.net code bounties have been fairly successful this year - two of
> the five projects have been completed, and the large "vmware 6 on FreeBSD"
> project is now underway.
> We'd like to add a new bounty for this kern.ngroups issue. We are posting
> to -hackers today to get some feedback on how long this will take and how
> much money might reasonably be expected to lure this work.
> --rsync.net Support
>  Is it indeed true that these programs are broken by not following
> NGROUPS_MAX from syslimits.h?
I don't see how they can be broken. They may not see more than 16
groups, but they shouldn't blow up. The only possibility of bad usage I
see is something like this:
gidsetlen = getgroups(0, NULL);
But I guess the most common use is:
gidsetlen = getgroups(NGROUPS_MAX, gids);
Binaries using the latter method should be just fine.
BTW. The latter method is what all utilities from the base system use.
Pawel Jakub Dawidek http://www.wheel.pl
pjd at FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20070927/5ff543d9/attachment.pgp
More information about the freebsd-hackers