diff options
| author | Adrian DC <radian.dc@gmail.com> | 2020-12-30 20:11:24 +0100 |
|---|---|---|
| committer | Adrian DC <radian.dc@gmail.com> | 2020-12-30 22:41:33 +0100 |
| commit | 2b34a0e919d079c76bac5d3a5ed98294e27aad39 (patch) | |
| tree | 720b7bb46ef4536336c9887d8a3fc790ba60d43b /code_coverage/seccomp_policy/code_coverage.arm64.policy | |
| parent | e7327ef122e88d949e568605ac35ea09d45e42cb (diff) | |
init: Sort the list of flattened APEX folders to avoid variations
* In 'ActivateFlattenedApexesFrom', the 'readdir' detects
the APEX folders in a random way that depends on filesystems,
built packages and order of the build chain
* In normal cases, this is not an issue, however when building
with Go configurations, we have a case where the package
'com.android.tethering.inprocess' is built along the
'com.android.tethering' overriden binary, and depending on
the 'readdir' output, the mounts break the Tethering service
Change-Id: I8ac4a0284d8d885f732c71e846933869cf16a0bd
Signed-off-by: Adrian DC <radian.dc@gmail.com>
Diffstat (limited to 'code_coverage/seccomp_policy/code_coverage.arm64.policy')
0 files changed, 0 insertions, 0 deletions