public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joe Simmons-Talbott <josimmon@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] vfprintf-internal: Replace alloca with malloc.
Date: Mon, 15 May 2023 14:49:37 -0400	[thread overview]
Message-ID: <20230515184937.GB176347@oak> (raw)
In-Reply-To: <35611aa1-595d-4158-9fea-672eafcde388@redhat.com>

On Mon, May 15, 2023 at 02:35:36PM -0400, Carlos O'Donell wrote:
> 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?

I used 'git format-patch' but then removed a blank line that the patch
added during 'git send-email --annotate'.  Sorry.  I'll post a v3
shortly.

Thanks,
Joe


      reply	other threads:[~2023-05-15 18:49 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
2023-05-15 18:49   ` Joe Simmons-Talbott [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=20230515184937.GB176347@oak \
    --to=josimmon@redhat.com \
    --cc=carlos@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).