From: Carlos O'Donell <carlos@redhat.com>
To: Joe Simmons-Talbott <josimmon@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] vfprintf-internal: Replace alloca with malloc.
Date: Mon, 15 May 2023 14:35:36 -0400 [thread overview]
Message-ID: <35611aa1-595d-4158-9fea-672eafcde388@redhat.com> (raw)
In-Reply-To: <20230510153230.2207571-1-josimmon@redhat.com>
On 5/10/23 11:32, Joe Simmons-Talbott via Libc-alpha wrote:
> Avoid potential stack overflow from unbounded alloca.
This fails to apply in pre-commit CI e.g. error: corrupt patch at line 145
How did you generate this patch?
> ---
> Changes to v1:
> * Don't check pointer before calling free()
> * Move deallocation code after the all_done label
>
> stdio-common/vfprintf-internal.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/stdio-common/vfprintf-internal.c b/stdio-common/vfprintf-internal.c
> index c76c06e49b..58c21481ce 100644
> --- a/stdio-common/vfprintf-internal.c
> +++ b/stdio-common/vfprintf-internal.c
> @@ -1001,6 +1001,7 @@ printf_positional (struct Xprintf_buffer * buf, const CHAR_T *format,
> scratch_buffer_init (&specsbuf);
> struct printf_spec *specs = specsbuf.data;
> size_t specs_limit = specsbuf.length / sizeof (specs[0]);
> + bool malloced_pa_user = false;
>
> /* Used as a backing store for args_value, args_size, args_type
> below. */
> @@ -1171,7 +1172,10 @@ printf_positional (struct Xprintf_buffer * buf, const CHAR_T *format,
> else if (__glibc_unlikely (__printf_va_arg_table != NULL)
> && __printf_va_arg_table[args_type[cnt] - PA_LAST] != NULL)
> {
> - args_value[cnt].pa_user = alloca (args_size[cnt]);
> + args_value[cnt].pa_user = malloc (args_size[cnt]);
> + if (args_value[cnt].pa_user == NULL)
> + break;
> + malloced_pa_user = true;
> (*__printf_va_arg_table[args_type[cnt] - PA_LAST])
> (args_value[cnt].pa_user, ap_savep);
> }
> @@ -1334,7 +1338,11 @@ printf_positional (struct Xprintf_buffer * buf, const CHAR_T *format,
> (specs[nspecs_done].next_fmt
> - specs[nspecs_done].end_of_fmt));
> }
> all_done:
> + if (malloced_pa_user)
> + for (cnt = 0; cnt < nargs; ++cnt)
> + free (args_value[cnt].pa_user);
> scratch_buffer_free (&argsbuf);
> scratch_buffer_free (&specsbuf);
> }
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-05-15 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 15:32 Joe Simmons-Talbott
2023-05-15 18:35 ` Carlos O'Donell [this message]
2023-05-15 18:49 ` Joe Simmons-Talbott
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=35611aa1-595d-4158-9fea-672eafcde388@redhat.com \
--to=carlos@redhat.com \
--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).