selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Cc: Nicolas Iooss <nicolas.iooss@m4x.org>
Subject: Re: [PATCH v2] libsemanage: genhomedircon - improve handling large groups
Date: Fri, 15 Feb 2019 14:56:41 +0100	[thread overview]
Message-ID: <pjd1s49noiu.fsf@redhat.com> (raw)
In-Reply-To: <CAJfZ7=kFKx6cz1Tj1impdii4iDKfKtC_LffBTW3Rfg1fEJkHzA@mail.gmail.com> (Nicolas Iooss's message of "Tue, 12 Feb 2019 22:02:18 +0100")

Nicolas Iooss <nicolas.iooss@m4x.org> writes:

> On Tue, Feb 12, 2019 at 4:20 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> getgrnam_r() uses a preallocated buffer to store a structure containing
>> the broken-out fields of the record in the group database. The size of
>> this buffer is usually sysconf(_SC_GETGR_R_SIZE_MAX) == 1024 and it is
>> not enough for groups with a large number of users.  In these cases,
>> getgrnam_r() returns -1 and sets errno to ERANGE and the caller can
>> retry with a larger buffer.
>>
>> Fixes:
>> $ semanage login -a -s user_u -r s0-s0:c1.c2 '%largegroup'
>> libsemanage.semanage_direct_commit: semanage_genhomedircon returned error code -1. (Numerical result out of range).
>> OSError: Numerical result out of range
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>

Merged.

>> ---
>>  libsemanage/src/genhomedircon.c | 20 +++++++++++++++++---
>>  1 file changed, 17 insertions(+), 3 deletions(-)
>>
>> diff --git a/libsemanage/src/genhomedircon.c b/libsemanage/src/genhomedircon.c
>> index 591941fb..e5f8d371 100644
>> --- a/libsemanage/src/genhomedircon.c
>> +++ b/libsemanage/src/genhomedircon.c
>> @@ -1077,10 +1077,24 @@ static int get_group_users(genhomedircon_settings_t * s,
>>
>>         const char *grname = selogin + 1;
>>
>> -       if (getgrnam_r(grname, &grstorage, grbuf,
>> -                       (size_t) grbuflen, &group) != 0) {
>> -               goto cleanup;
>> +       errno = 0;
>> +       while (
>> +               (retval = getgrnam_r(grname, &grstorage, grbuf, (size_t) grbuflen, &group)) != 0 &&
>> +               errno == ERANGE
>> +       ) {
>> +               char *new_grbuf;
>> +               grbuflen *= 2;
>> +               if (grbuflen < 0)
>> +                       /* the member list could exceed 2Gb on a system with a 32-bit CPU (where
>> +                        * sizeof(long) = 4) - if this ever happened, the loop would become infinite. */
>> +                       goto cleanup;
>> +               new_grbuf = realloc(grbuf, grbuflen);
>> +               if (new_grbuf == NULL)
>> +                       goto cleanup;
>> +               grbuf = new_grbuf;
>>         }
>> +       if (retval != 0)
>> +               goto cleanup;
>>
>>         if (group == NULL) {
>>                 ERR(s->h_semanage, "Can't find group named %s\n", grname);
>> --
>> 2.20.1
>>

      reply	other threads:[~2019-02-15 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 19:45 [PATCH] libsemanage: genhomedircon - improve handling large groups Petr Lautrbach
2019-02-07 21:19 ` Nicolas Iooss
2019-02-08 16:46   ` Petr Lautrbach
2019-02-12 15:20     ` [PATCH v2] " Petr Lautrbach
2019-02-12 21:02       ` Nicolas Iooss
2019-02-15 13:56         ` Petr Lautrbach [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=pjd1s49noiu.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=nicolas.iooss@m4x.org \
    --cc=selinux@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;
as well as URLs for NNTP newsgroup(s).