From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org,
Joe Simmons-Talbott <josimmon@redhat.com>
Subject: Re: [PATCH v6] ifaddrs: Get rid of alloca
Date: Mon, 26 Jun 2023 09:10:29 -0400 [thread overview]
Message-ID: <08935c76-f659-7419-f092-8c700c16a7ed@gotplt.org> (raw)
In-Reply-To: <ccd8858c-985a-f7ce-6de9-310526a6803b@linaro.org>
On 2023-06-22 09:47, Adhemerval Zanella Netto via Libc-alpha wrote:
>
>
> On 21/06/23 17:00, Joe Simmons-Talbott via Libc-alpha wrote:
>> Use scratch_buffer and malloc rather than alloca to avoid potential stack
>> overflows.
>
> LGTM, thanks.
>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Adhemerval, would it make sense to have Joe request write access to the
repository so that he can push his patches? Would you sponsor him?
Thanks,
Sid
next prev parent reply other threads:[~2023-06-26 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 20:00 Joe Simmons-Talbott
2023-06-22 13:47 ` Adhemerval Zanella Netto
2023-06-26 13:10 ` Siddhesh Poyarekar [this message]
2023-06-26 19:49 ` Adhemerval Zanella Netto
2023-06-26 21:04 ` Joe Simmons-Talbott
2023-06-27 11:50 ` Siddhesh Poyarekar
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=08935c76-f659-7419-f092-8c700c16a7ed@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=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).