mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Kate Deplaix <kit-ty-kate@outlook.com>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [musl] [PATCH] Increase NGROUPS_MAX from 32 to 1024
Date: Fri, 13 Sep 2024 10:47:36 -0400	[thread overview]
Message-ID: <20240913144736.GZ10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <CWLP265MB41570C3A2B2E884E7659EB9CBC652@CWLP265MB4157.GBRP265.PROD.OUTLOOK.COM>

On Fri, Sep 13, 2024 at 11:45:13AM +0000, Kate Deplaix wrote:
> Hi,
> 
> Is there anything i can do to make a fix for this go forward?

What requirements are you still trying to satisfy? 3f49203c55cc made
it so initgroups accepts arbitrarily many groups independent of
NGROUPS_MAX.

My reading of POSIX is that the macro NGROUPS_MAX is a "minimum
maximum" that any instance of the implementation might impose, which
for us I think is the 32 imposed by old Linux.
sysconf(_SC_NGROUPS_MAX) does not yet expose a larger runtime max; is
that what you'd like to see happen?

Source I'm going on:
https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/limits.h.html
under the heading "Runtime Increasable Values".

Rich

  reply	other threads:[~2024-09-13 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 23:35 Kate Deplaix
2024-03-11 18:31 ` [musl] " Kate Deplaix
2024-03-12  0:46   ` Rich Felker
2024-04-09 12:54     ` Kate Deplaix
2024-04-09 15:46       ` Thorsten Glaser
2024-04-09 16:26         ` Rich Felker
2024-04-11  1:07 ` [musl] " Rich Felker
2024-04-11  1:51   ` Rich Felker
2024-04-11  2:58   ` Markus Wichmann
2024-04-11 11:44     ` Laurent Bercot
2024-09-13 11:45       ` Kate Deplaix
2024-09-13 14:47         ` Rich Felker [this message]
2024-09-13 16:00           ` Kate Deplaix
2024-09-13 16:12             ` Rich Felker
2024-09-13 18:34               ` Kate Deplaix

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=20240913144736.GZ10433@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=kit-ty-kate@outlook.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).