diff options
author | David Turner <digit@google.com> | 2020-08-05 10:50:06 +0200 |
---|---|---|
committer | Benjamin Kramer <benny.kra@googlemail.com> | 2020-08-05 10:51:48 +0200 |
commit | ba0e71432a60e1fa2da9e098cbc574a1d9b9618b (patch) | |
tree | 6d58b13a20561d8bddec368d267c1cb334f56266 /lldb/source/Plugins/ScriptInterpreter/Python | |
parent | f2916636f83dfeb4808a16045db0025783743471 (diff) | |
download | llvm-ba0e71432a60e1fa2da9e098cbc574a1d9b9618b.zip llvm-ba0e71432a60e1fa2da9e098cbc574a1d9b9618b.tar.gz llvm-ba0e71432a60e1fa2da9e098cbc574a1d9b9618b.tar.bz2 |
Do not map read-only data memory sections with EXECUTE flags.
The code in SectionMemoryManager.cpp unnecessarily maps
read-only data sections with the READ+EXECUTE flags. This is
undesirable from a security stand-point.
Moreover, on the Fuchsia platform, which is now very strict
about mapping pages with the EXECUTE permission, this simply
fails, because the section's pages were initially allocated
with only the READ+WRITE flags.
A more detailed description of the issue can be found in this
public SwiftShader bug:
https://issuetracker.google.com/issues/154586551
This patch just restrict the mapping to the READ flag for ROData
sections. Code sections are still mapped with READ+EXECUTE as
expected.
Reviewed By: lhames
Differential Revision: https://reviews.llvm.org/D78574
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions