[SERVER-26299] Evaluate feasibility and impact of clang's safe-stack sanitizer Created: 23/Sep/16  Updated: 02/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Per http://clang.llvm.org/docs/SafeStack.html. Potentially, this could be shippable too.



 Comments   
Comment by Andrew Morrow (Inactive) [ 22/Mar/21 ]

There are too many restrictions on using this for it to make sense to move forward under the current effort:

  • Doesn't support DSOs (not that big a deal, we don't ship that way, but inconvenient).
  • Doesn't work with mark/sweep GC, which probably makes it a non-starter for MozJS
  • We would need to tag our use of sigaltstack
  • libunwind uses ucontext.h, which isn't supported.

We should come back to this one when it is a little more approachable.

Comment by Andrew Morrow (Inactive) [ 25/Sep/16 ]

More info here: http://blog.includesecurity.com/2015/11/LLVM-SafeStack-buffer-overflowprotection.html

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