diff options
| author | Nikita Ioffe <ioffe@google.com> | 2020-06-22 17:47:23 +0100 |
|---|---|---|
| committer | Nikita Ioffe <ioffe@google.com> | 2020-06-24 16:30:03 +0100 |
| commit | a462044ac8c80141a45025ce52581ff331c771ec (patch) | |
| tree | 986aee1139478534f8d2b69771487e0e04aa1d64 /libutils/ProcessCallStack_fuzz.cpp | |
| parent | d9299c5119606fa4d2cc3a2483bd2e75201201e6 (diff) | |
Explicitly call restorecon_recursive on /metadata/apex
On some devices we see a weird in which /metadata/apex will have a wrong
selinux label. This will effectively prevent such devices from getting
any apex updates. Since we haven't figured out a root cause for this
bug, it's safer to explicitly call restorecon on /metadata/apex to make
sure it's correct.
This change shouldn't affect a normal boot flow, since /metadata/apex
will already have a correct label and restorecon_recursive will be a
no-op.
Test: rm -Rf /metadata/apex && \
mkdir /metadata/apex &&
mkdir /metadata/apex/sessions
Bug: 149317789
Merged-In: I971ffe35c93bb79d9e71106c24515ec0ee70333a
Change-Id: I971ffe35c93bb79d9e71106c24515ec0ee70333a
(cherry picked from commit cf7b6bad55b3c41d8289852488eb4496a4524ba5)
Diffstat (limited to 'libutils/ProcessCallStack_fuzz.cpp')
0 files changed, 0 insertions, 0 deletions