public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1970] New: getgrnam_r() and groups with more than 1024 bytes
Date: Fri, 02 Dec 2005 17:21:00 -0000	[thread overview]
Message-ID: <20051202172121.1970.burnus@gmx.de> (raw)

If I have a group with many entries (`/usr/bin/getent group test |wc -c
` > 1024), getgrnam() duely returns the entry whereas getgrnam_r() has some
troubles.

a) sysconf(_SC_GETGR_R_SIZE_MAX);
returns always 1024, which is not large enough, but as there is ENORANGE, it is
not too bad.
SUSv3: "_SC_GETGR_R_SIZE_MAX  Maximum size of getgrgid_r() and getgrnam_r() data
buffers" and "The maximum size needed for this buffer [3rd argument of
getgrnam_r] can be determined with the {_SC_GETGR_R_SIZE_MAX} sysconf() parameter."


b) Using  getgrnam_r() with a big group and a too small buffer =
_SC_GETGR_R_SIZE_MAX == 1024:
(i) group:  files  (in /etc/nsswitch.conf)
returned value: ERANGE, which is ok
(ii) group:  compat (in /etc/nsswitch.conf)
getgrnam_r crashes with a memory access error.
Expected: ERANGE or e.g. EIO.

c) Using  getgrnam_r() with a buffer bigger than 1024
(i) entry < 1024: Ok
(ii) entry > 1024 (independent of group:files vs. group:compat)
Memory access error

-- 
           Summary: getgrnam_r() and groups with more than 1024 bytes
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: burnus at gmx dot de
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: Compiled on a Linux 2.6.12 system on 2005-09-09.
  GCC host triplet: SUSE Linux 10.0 (i386) with kernel 2.6.14-
                    20051028140608-default
GCC target triplet: Configured for i686-suse-linux.


http://sourceware.org/bugzilla/show_bug.cgi?id=1970

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-12-02 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 17:21 burnus at gmx dot de [this message]
2005-12-09  7:11 ` [Bug libc/1970] " kukuk at suse dot de
2005-12-09 11:53 ` burnus at gmx dot de
2005-12-09 12:00 ` burnus at gmx dot de
2005-12-09 12:01 ` kukuk at suse dot de
2005-12-09 12:27 ` burnus at gmx dot de
2005-12-30 20:52 ` drepper at redhat dot com
2006-04-23 19:47 ` drepper at redhat dot com

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=20051202172121.1970.burnus@gmx.de \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).