summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPat Erley <perley@cyngn.com>2016-04-19 11:34:09 -0700
committerGerrit Code Review <gerrit@cyanogenmod.org>2016-04-22 13:09:37 -0700
commitda1a9004f8f64369b7e443ab11b4e2581d039a5e (patch)
treec50b0c994f7c8055d50c0817a09ae673310e4469
parentb110c513442381270ee340e14e584d61b5b102a7 (diff)
downloadvendor_replicant-da1a9004f8f64369b7e443ab11b4e2581d039a5e.zip
vendor_replicant-da1a9004f8f64369b7e443ab11b4e2581d039a5e.tar.gz
vendor_replicant-da1a9004f8f64369b7e443ab11b4e2581d039a5e.tar.bz2
sepolicy: Allow recovery to mount on tmpfs
/storage is a tmpfs volume, and is where updater stores its zip when downloading updates. Devices with emmc partitions that are used as 'sdcard' volumes will end up with paths like: /storage/UUID/...../update.zip where UUID is the mount point for the partition and update.zip is the downloaded update. With this change, minivold can create the UUID folder and mount onto it, fixing the application of updates. Change-Id: I4fa84fd590f5ff0f91e38c49cef0c179728fdf43
-rw-r--r--sepolicy/recovery.te1
1 files changed, 1 insertions, 0 deletions
diff --git a/sepolicy/recovery.te b/sepolicy/recovery.te
index da6ddac..c5f58c6 100644
--- a/sepolicy/recovery.te
+++ b/sepolicy/recovery.te
@@ -19,6 +19,7 @@ allow recovery rootfs:file link;
allow recovery rootfs:dir { write create rmdir add_name remove_name };
# Read storage files and directories
+allow recovery tmpfs:dir mounton;
allow recovery media_rw_data_file:dir r_dir_perms;
allow recovery media_rw_data_file:file r_file_perms;
allow recovery vfat:dir r_dir_perms;