public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joe Simmons-Talbott <josimmon@redhat.com>
To: Arjun Shankar <arjun@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] nss: Get rid of alloca usage in makedb's write_output.
Date: Wed, 4 Oct 2023 10:00:01 -0400	[thread overview]
Message-ID: <20231004140001.GH4098455@oak> (raw)
In-Reply-To: <CAG_osaa6AY1BsW7zn6Q1O789Vu7VGMDXCVvPsEWyTuBHk4aFqg@mail.gmail.com>

On Wed, Oct 04, 2023 at 03:09:14PM +0200, Arjun Shankar wrote:
> Hi Joe,
> 
> > Replace alloca usage with a scratch_buffer.
> > ---
> > Changes to v1:
> >  * move scratch_buffer_free after the call to error ().
> >
> >  nss/makedb.c | 14 +++++++++++++-
> >  1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/nss/makedb.c b/nss/makedb.c
> > index 48c8fe1333..67c3c4c893 100644
> > --- a/nss/makedb.c
> > +++ b/nss/makedb.c
> > @@ -25,6 +25,7 @@
> >  #include <inttypes.h>
> >  #include <libintl.h>
> >  #include <locale.h>
> > +#include <scratch_buffer.h>
> >  #include <search.h>
> >  #include <stdbool.h>
> >  #include <stdio.h>
> 
> OK.
> 
> > @@ -739,7 +740,16 @@ write_output (int fd)
> >    struct nss_db_header *header;
> >    uint64_t file_offset = (sizeof (struct nss_db_header)
> >                           + (ndatabases * sizeof (header->dbs[0])));
> > -  header = alloca (file_offset);
> > +  struct scratch_buffer sbuf;
> > +  scratch_buffer_init (&sbuf);
> > +
> > +
> > +  if (!scratch_buffer_set_array_size (&sbuf, 1, file_offset))
> > +    {
> > +      error (0, errno, gettext ("failed to allocate memory"));
> > +      return EXIT_FAILURE;
> > +    }
> 
> The way scratch_buffer_init and scratch_buffer_set_array_size are
> implemented currently, a failure of the set_array_size here looks like
> it doesn't necessarily need a scratch_buffer_free to be called after
> failure because there's nothing to be freed. But I think calling
> scratch_buffer_free here before returning here is the safer bet.
> 

I haven't been including a scratch_buffer_free call on failure of
scratch_buffer_set_array_size.  Both failure code paths for
scratch_buffer_set_array_size reset the buffer to the default character
array and any heap allocated storage is freed.  If there is agreement
that a call to scratch_buffer_free is desired I'm happy to add it.

Thanks,
Joe


  reply	other threads:[~2023-10-04 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 14:11 Joe Simmons-Talbott
2023-10-04 13:09 ` Arjun Shankar
2023-10-04 14:00   ` Joe Simmons-Talbott [this message]
2023-10-04 15:27     ` Arjun Shankar

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=20231004140001.GH4098455@oak \
    --to=josimmon@redhat.com \
    --cc=arjun@redhat.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).