service.sh: Restore SELinux labels on DP data directory during boot #600
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OxygenOS on OnePlus devices seems to create the /data/user_de/0/<id> directory with the wrong SELinux label initially. However, once the correct label is set, it persists just fine. Despite it persisting, we still need to run restorecon during boot instead of during installation because it requires PackageManager to already be aware of BCR. Fixes: #582 Fixes: #591 Fixes: #598 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
chenxiaolong
added a commit
that referenced
this pull request
Sep 9, 2024
Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OxygenOS on OnePlus devices seems to create the
/data/user_de/0/<id>directory with the wrong SELinux label initially. However, once the correct label is set, it persists just fine. Despite it persisting, we still need to run restorecon during boot instead of during installation because it requires PackageManager to already be aware of BCR.Fixes: #582
Fixes: #591
Fixes: #598