From: Florian Weimer <fw@deneb.enyo.de>
To: Joe Simmons-Talbott via Libc-alpha <libc-alpha@sourceware.org>
Cc: Joe Simmons-Talbott <josimmon@redhat.com>
Subject: Re: [PATCH v2] mips: dl-machine-reject-phdr: Get rid of alloca.
Date: Sun, 25 Jun 2023 14:20:03 +0200 [thread overview]
Message-ID: <87h6qv68ek.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20230623172415.3495004-1-josimmon@redhat.com> (Joe Simmons-Talbott via Libc-alpha's message of "Fri, 23 Jun 2023 13:24:15 -0400")
* Joe Simmons-Talbott via Libc-alpha:
> Use a scratch_buffer rather than alloca to avoid potential stack
> overflow.
You don't need a scratch buffer anymore. Just read into the struct
directly.
Thanks,
Florian
next prev parent reply other threads:[~2023-06-25 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 17:24 Joe Simmons-Talbott
2023-06-25 12:20 ` Florian Weimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 13:49 Joe Simmons-Talbott
2023-06-23 16:26 ` Florian Weimer
2023-06-23 17:28 ` Joe Simmons-Talbott
2023-06-23 17:34 ` 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=87h6qv68ek.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).