public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Joe Simmons-Talbott <josimmon@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] fxprintf: Get rid of alloca
Date: Wed, 19 Jul 2023 15:12:43 -0300	[thread overview]
Message-ID: <e7636e36-9bf3-5e90-ee0b-cf770954e9c1@linaro.org> (raw)
In-Reply-To: <20230707175349.2096131-1-josimmon@redhat.com>



On 07/07/23 14:53, Joe Simmons-Talbott via Libc-alpha wrote:
> Use a scratch_buffer rather than alloca/malloc to avoid potential stack
> overflow.

LGTM, thanks.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

> ---
>  stdio-common/fxprintf.c | 14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)
> 
> diff --git a/stdio-common/fxprintf.c b/stdio-common/fxprintf.c
> index f0ac9654ab..88501ab61f 100644
> --- a/stdio-common/fxprintf.c
> +++ b/stdio-common/fxprintf.c
> @@ -15,6 +15,7 @@
>     License along with the GNU C Library; if not, see
>     <https://www.gnu.org/licenses/>.  */
>  
> +#include <scratch_buffer.h>
>  #include <stdarg.h>
>  #include <stdio.h>
>  #include <stdlib.h>
> @@ -34,20 +35,18 @@ locked_vfxprintf (FILE *fp, const char *fmt, va_list ap,
>    wchar_t *wfmt;
>    mbstate_t mbstate;
>    int res;
> -  int used_malloc = 0;
>    size_t len = strlen (fmt) + 1;
> +  struct scratch_buffer buf;
> +  scratch_buffer_init (&buf);
>  
>    if (__glibc_unlikely (len > SIZE_MAX / sizeof (wchar_t)))
>      {
>        __set_errno (EOVERFLOW);
>        return -1;
>      }

This check is redundant, but scratch_buffer_set_array_size would return
ENOMEM in this case.  I guess it should not change this for now.

> -  if (__libc_use_alloca (len * sizeof (wchar_t)))
> -    wfmt = alloca (len * sizeof (wchar_t));
> -  else if ((wfmt = malloc (len * sizeof (wchar_t))) == NULL)
> +  if (!scratch_buffer_set_array_size (&buf, sizeof (wchar_t), len))
>      return -1;
> -  else
> -    used_malloc = 1;
> +  wfmt = buf.data;
>  
>    memset (&mbstate, 0, sizeof mbstate);
>    res = __mbsrtowcs (wfmt, &fmt, len, &mbstate);
> @@ -55,8 +54,7 @@ locked_vfxprintf (FILE *fp, const char *fmt, va_list ap,
>    if (res != -1)
>      res = __vfwprintf_internal (fp, wfmt, ap, mode_flags);
>  
> -  if (used_malloc)
> -    free (wfmt);
> +  scratch_buffer_free (&buf);
>  
>    return res;
>  }

  reply	other threads:[~2023-07-19 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 17:53 Joe Simmons-Talbott
2023-07-19 18:12 ` Adhemerval Zanella Netto [this message]
2023-08-10 13:34   ` Joe Simmons-Talbott
2023-09-06 16:56     ` Adhemerval Zanella Netto

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=e7636e36-9bf3-5e90-ee0b-cf770954e9c1@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=josimmon@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).