ACPR/android_system_core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge "Explicitly call restorecon_recursive on /metadata/apex" am: 5b2457ed34

Browse source 
Original change: https://android-review.googlesource.com/c/platform/system/core/+/1348884

Change-Id: I42ac96691e09e203976c0c804da0132ba4053ccc
This commit is contained in:
Nikita Ioffe 2020-06-24 17:00:40 +00:00 • committed by Automerger Merge Worker
commit b3a10e5220
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
rootdir/init.rc
View file

@ -520,6 +520,13 @@ on post-fs
mkdir /metadata/apex 0700 root system
mkdir /metadata/apex/sessions 0700 root system
# On some devices we see a weird behaviour in which /metadata/apex doesn't
# have a correct label. To workaround this bug, explicitly call restorecon
# on /metadata/apex. For most of the boot sequences /metadata/apex will
# already have a correct selinux label, meaning that this call will be a
# no-op.
restorecon_recursive /metadata/apex
on late-fs
# Ensure that tracefs has the correct permissions.
# This does not work correctly if it is called in post-fs.