commit 9a4a45762219f43903f54d5f29157dc6b3881557
author Jeff Sharkey <jsharkey@android.com> Fri Apr 14 16:28:59 2017 -0600
committer Jeff Sharkey <jsharkey@android.com> Fri Apr 14 16:29:04 2017 -0600
tree e3dcbc3002454f5a3ef144a428b1a7154c507ff7
parent 43112fd26e89b0b27b968c54d9d8d45928f8304e

Clear identity to handle ALLOCATE_AGGRESSIVE.

We're not actually clearing any files, only deciding how much free
space is available, so we're fine assuming the remote caller has the
permission.

Test: builds, boots
Bug: 37169076
Change-Id: I6cd42f77c43e9d2de40e2b8b937c7f2145f1b869

data/etc/privapp-permissions-platform.xml

diff --git a/data/etc/privapp-permissions-platform.xml b/data/etc/privapp-permissions-platform.xml
index ec653d0..7f07f03 100644
--- a/data/etc/privapp-permissions-platform.xml
+++ b/data/etc/privapp-permissions-platform.xml
@@ -40,6 +40,7 @@
 
     <privapp-permissions package="com.android.defcontainer">
         <permission name="android.permission.ACCESS_CACHE_FILESYSTEM"/>
+        <permission name="android.permission.ALLOCATE_AGGRESSIVE"/>
         <permission name="android.permission.INTERACT_ACROSS_USERS"/>
         <permission name="android.permission.WRITE_MEDIA_STORAGE"/>
     </privapp-permissions>