From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-arm@nongnu.org, "Glenn Miles" <milesg@linux.ibm.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 0/4] system: Forbid alloca()
Date: Tue, 10 Jun 2025 11:29:57 +0200 [thread overview]
Message-ID: <b85339d1-4347-4ac5-b0ba-47c9e941f28c@linaro.org> (raw)
In-Reply-To: <20250605193540.59874-1-philmd@linaro.org>
On 5/6/25 21:35, Philippe Mathieu-Daudé wrote:
> Eradicate alloca() uses on system code, then enable
> -Walloca to prevent new ones to creep back in.
>
> Philippe Mathieu-Daudé (4):
> hw/gpio/pca9552: Avoid using g_newa()
> backends/tpmL Avoid using g_alloca()
> tests/unit/test-char: Avoid using g_alloca()
Patches 1-3 queued.
prev parent reply other threads:[~2025-06-10 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 19:35 [PATCH 0/4] system: Forbid alloca() Philippe Mathieu-Daudé
2025-06-05 19:35 ` [PATCH 1/4] hw/gpio/pca9552: Avoid using g_newa() Philippe Mathieu-Daudé
2025-06-05 21:03 ` Miles Glenn
2025-06-05 19:35 ` [PATCH 2/4] backends/tpmL Avoid using g_alloca() Philippe Mathieu-Daudé
2025-06-05 21:23 ` BALATON Zoltan
2025-06-06 7:00 ` Philippe Mathieu-Daudé
2025-06-06 8:14 ` Thomas Huth
2025-06-08 19:09 ` Stefan Berger
2025-06-08 19:07 ` Stefan Berger
2025-06-05 19:35 ` [PATCH 3/4] tests/unit/test-char: " Philippe Mathieu-Daudé
2025-06-05 20:53 ` Pierrick Bouvier
2025-06-06 6:09 ` Philippe Mathieu-Daudé
2025-06-06 16:18 ` Pierrick Bouvier
2025-06-05 19:35 ` [RFC PATCH 4/4] buildsys: Prohibit alloca() use on system code Philippe Mathieu-Daudé
2025-06-05 20:53 ` [PATCH 0/4] system: Forbid alloca() Pierrick Bouvier
2025-06-06 8:37 ` Peter Maydell
2025-06-06 8:53 ` Philippe Mathieu-Daudé
2025-06-06 8:44 ` Alex Bennée
2025-06-09 13:46 ` Stefan Hajnoczi
2025-06-10 9:29 ` Philippe Mathieu-Daudé [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=b85339d1-4347-4ac5-b0ba-47c9e941f28c@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=milesg@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
/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 NNTP newsgroup(s).