diff options
author | Jiyong Park <jiyong@google.com> | 2019-01-28 19:47:32 +0900 |
---|---|---|
committer | Jiyong Park <jiyong@google.com> | 2019-01-29 07:10:31 +0900 |
commit | 388ef3f5aacd8023102a076e81be14bc1a62a294 (patch) | |
tree | 54abefda09f30d61a951de2ac75cd526ac6aeb71 /python/python.go | |
parent | ee0413915438f2cfe1b84ae4be64d3974e80be85 (diff) |
Create sanitizer variants of APEX only when SANITIZE_TARGET is set
This fixes a problem that APEX is unconditionally mutated for all
sanitizer types. This can make an APEX to include sanitized version
of a lib even when SANITIZE_TARGET is not set. It can happen when lib X
is directly depended on by an APEX (e.g. via native_shared_libs) and X
has a sanitized variant due to the dependency from another library Y
which is force sanitized (via 'sanitize' property). In that case,
regardless of lib Y is in the APEX or not, the APEX chooses the
sanitized variant of lib X since the dependency from APEX to the lib is
created with AddFarVariationDependency.
Fixing this problem by mutating the APEX for a sanitizer type only when
the device is requested to be sanitized.
Bug: 122717287
Test: add libnetd_client to com.android.runtime APEX.
Inspect build.ninja to verify that libnetd_client.so in the runtime APEX
is not a sanitized one.
Change-Id: I918bc8407137d74c5456142b3a29de13df68c0b3
Diffstat (limited to 'python/python.go')
0 files changed, 0 insertions, 0 deletions