Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 4920a707 authored by Nikita Ioffe's avatar Nikita Ioffe Committed by Automerger Merge Worker
Browse files

Merge "Explicitly call restorecon_recursive on /metadata/apex" into rvc-dev... 

Merge "Explicitly call restorecon_recursive on /metadata/apex" into rvc-dev am: 6a8602a8 am: d9469bdc am: 40707d75 am: 63add3aa

Original change: https://googleplex-android-review.googlesource.com/c/platform/system/core/+/11955299

Change-Id: Ibfd6099e22414fa73dc17774383c019c7b991929
parents 2294d257 63add3aa

rootdir/init.rc

+6 −0
Original line number Diff line number Diff line
@@ -520,6 +520,12 @@ 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



    mkdir /metadata/staged-install 0770 root system

on late-fs