From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH v2 0/2] topic: meson: add more compiler hardening flags
Date: Wed, 3 Jan 2024 12:34:12 +0000 [thread overview]
Message-ID: <20240103123414.2401208-1-berrange@redhat.com> (raw)
This brings more compiler hardening flags to the default QEMU
build process. The proposed flags have already been adopted by
default in the kernel build process. At some point it is hoped
that distros might enable them globally, as they've done in
the past with things like _FORTIFY_SOURCE. Meanwhile they are
easy things to enable in QEMU which have negligible cost and
clear benefits to hardening. Considering QEMU shows no signs
of stoppping the flow of guest triggerable CVEs, investing in
hardening is worthwhile. See the respective commit messages
for details
Changed in v2:
* Fix spelling of -ftrivial-auto-var-init option
Daniel P. Berrangé (2):
meson: mitigate against ROP exploits with -fzero-call-used-regs
meson: mitigate against use of uninitialize stack for exploits
meson.build | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--
2.43.0
next reply other threads:[~2024-01-03 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 12:34 Daniel P. Berrangé [this message]
2024-01-03 12:34 ` [PATCH v2 1/2] meson: mitigate against ROP exploits with -fzero-call-used-regs Daniel P. Berrangé
2024-01-09 14:54 ` Markus Armbruster
2024-01-09 15:12 ` Daniel P. Berrangé
2024-01-11 12:03 ` Markus Armbruster
2024-01-03 12:34 ` [PATCH v2 2/2] meson: mitigate against use of uninitialize stack for exploits Daniel P. Berrangé
2024-01-09 14:48 ` Markus Armbruster
2024-01-09 14:53 ` Daniel P. Berrangé
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=20240103123414.2401208-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).