commit | 07bc2f67ad6e4b090941cd9a00b823b25a5eaccc | [log] [tgz] |
---|---|---|
author | Drew Fisher <zarvox@google.com> | Wed Apr 17 23:30:15 2019 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Apr 17 23:30:15 2019 +0000 |
tree | b176c3dd705111cf058eaaf651fb909d81c6a5e7 | |
parent | bcbc2d906fb02802142307e6d1b773dea798c94c [diff] |
[fdio] Lift zx_vmo_replace_as_executable out of fdio_get_vmo_* Today, anything calling any of these methods is getting a VMO that is marked executable. Not every caller actually needs an executable VMO; generally only things that try to launch other programs need this. The fdio_get_vmo_* calls are documented as returning a read-only, non-executable VMO; however, as far as I can tell, they have never actually done so. To whittle down the overuse of executable VMOs, we can push the "mark things executable" responsiblity up to various callers. After some digging, I believe this changeset covers the universe of launchers and loaders that need executable VMOs in the Fuchsia tree. Tests: paved and booted astro successfully Bug: SEC-252 #comment Lift zx_vmo_replace_as_executable out of fdio_get_vmo_* Change-Id: Ieb6e0c5c12dff152b1cd57cd736bb25df5989332
Pink + Purple == Fuchsia (a new operating system)
Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.
Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.
See Getting Started.
See the documentation.