topic: meson: add more compiler hardening flags
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 5 repliesIn review
- v12 patches 6 repliesSuperseded
Changes in v2 from the cover letter
* Fix spelling of -ftrivial-auto-var-init option
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | meson: mitigate against ROP exploits with -fzero-call-used-regsmeson.build | +11 | 3 replies | |
| 2/2 | meson: mitigate against use of uninitialize stack for exploitsmeson.build | +5 | 2 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Thomas Huth |
|---|---|
| 1/2 | R-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/2] topic: meson: add more compiler hardening flags
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(+)
Signature · 1 line
2.43.0