[SERVER-36176] Evaluate feasibility and impact of -fstack-clash-protection Created: 18/Jul/18  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: former-toolchain-epic
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Per SERVER-35935 and https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc/, there are some new hardening flags in GCC 8 that we should investigate. This ticket tracks that work for --fstack-clash-protection



 Comments   
Comment by Githook User [ 23/Mar/21 ]

Author:

{'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}

Message: SERVER-36176 Add an experiment to enable support for -fstack-clash-protection
Branch: master
https://github.com/mongodb/mongo/commit/b212554d5ef3b35bc05f8b9ffadadc2bf1f25b6d

Generated at Thu Feb 08 04:42:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.