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

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

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

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

Change-Id: I42ac96691e09e203976c0c804da0132ba4053ccc
parents fc10e3f8 5b2457ed

rootdir/init.rc

+7 −0
Original line number Diff line number Diff line
@@ -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.