From 7ef348b1bac77418862f7c22ecefb51ec3517808 Mon Sep 17 00:00:00 2001 From: Nick Kralevich Date: Fri, 16 Jan 2015 11:58:05 -0800 Subject: [PATCH] Revert "isolated_app: Do not allow access to the gpu_device." Chrome team recommends reverting this patch and introducing it into a future version of Android, to avoid potential compatibility issues. This reverts commit 9de62d6ffed14a6b0abed63d2a915cdae87a7fc4. Bug: 17471434 Bug: 18609318 Change-Id: I3086cb8a8d7142b1eadce622f7e87a4c3426b6bf --- app.te | 2 +- isolated_app.te | 3 --- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/app.te b/app.te index b8b9066c1..4abf5944f 100644 --- a/app.te +++ b/app.te @@ -90,7 +90,7 @@ allow appdomain qtaguid_device:chr_file r_file_perms; # Grant GPU access to all processes started by Zygote. # They need that to render the standard UI. -allow { appdomain -isolated_app } gpu_device:chr_file { rw_file_perms execute }; +allow appdomain gpu_device:chr_file { rw_file_perms execute }; # Use the Binder. binder_use(appdomain) diff --git a/isolated_app.te b/isolated_app.te index a035901b7..a156838bb 100644 --- a/isolated_app.te +++ b/isolated_app.te @@ -13,9 +13,6 @@ type isolated_app, domain; app_domain(isolated_app) net_domain(isolated_app) -# Isolated apps shouldn't be able to access the driver directly. -neverallow isolated_app gpu_device:file { rw_file_perms execute }; - # read and write access to app_data_file is already # granted via app.te. Allow execute. # Needed to allow dlopen() from Chrome renderer processes.