From: Carlos O'Donell <carlos@redhat.com>
To: Joe Simmons-Talbott <josimmon@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] vfprintf-internal: Get rid of alloca.
Date: Thu, 18 May 2023 10:08:31 -0400 [thread overview]
Message-ID: <a24fcbce-5a92-86ab-b759-7e7b0259520a@redhat.com> (raw)
In-Reply-To: <20230517212847.1821277-1-josimmon@redhat.com>
On 5/17/23 17:28, Joe Simmons-Talbott via Libc-alpha wrote:
> Avoid potential stack overflow from unbounded alloca. Use the existing
> scratch_buffer instead.
Fails 32-bit i686 CI:
https://patchwork.sourceware.org/project/glibc/patch/20230517212847.1821277-1-josimmon@redhat.com/
Please have a look.
> ---
> stdio-common/vfprintf-internal.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/stdio-common/vfprintf-internal.c b/stdio-common/vfprintf-internal.c
> index c76c06e49b..baaefb763a 100644
> --- a/stdio-common/vfprintf-internal.c
> +++ b/stdio-common/vfprintf-internal.c
> @@ -1066,6 +1066,8 @@ printf_positional (struct Xprintf_buffer * buf, const CHAR_T *format,
> union printf_arg *args_value;
> int *args_size;
> int *args_type;
> + int *args_pa_user;
> + size_t args_pa_user_offset;
> {
> /* Calculate total size needed to represent a single argument
> across all three argument-related arrays. */
> @@ -1082,6 +1084,7 @@ printf_positional (struct Xprintf_buffer * buf, const CHAR_T *format,
> now. */
> args_size = &args_value[nargs].pa_int;
> args_type = &args_size[nargs];
> + args_pa_user = &args_type[nargs];
> memset (args_type, (mode_flags & PRINTF_FORTIFY) != 0 ? '\xff' : '\0',
> nargs * sizeof (*args_type));
> }
> @@ -1171,7 +1174,24 @@ 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]);
> + if (args_pa_user > argsbuf + args_size)
> + {
> + args_pa_user_offset = args_pa_user - &args_type[nargs];
> + if (!scratch_buffer_grow_preserve (&argsbuf))
> + {
> + Xprintf_buffer_mark_failed (buf);
> + goto all_done;
> + }
> + args_value = argsbuf.data;
> + /* Set up the remaining two arrays to each point past the end of
> + the prior array, since space for all three has been allocated
> + now. */
> + args_size = &args_value[nargs].pa_int;
> + args_type = &args_size[nargs];
> + args_pa_user = &args_type[nargs] + args_pa_user_offset;
> + }
> + args_value[cnt].pa_user = args_pa_user;
> + args_pa_user += args_size[cnt];
> (*__printf_va_arg_table[args_type[cnt] - PA_LAST])
> (args_value[cnt].pa_user, ap_savep);
> }
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-05-18 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 21:28 Joe Simmons-Talbott
2023-05-18 14:08 ` Carlos O'Donell [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=a24fcbce-5a92-86ab-b759-7e7b0259520a@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).