platform_system_sepolicy/private/file_contexts_asan

/data/asan/system/lib(/.*)?                u:object_r:system_file:s0
/data/asan/system/lib64(/.*)?              u:object_r:system_file:s0
/data/asan/vendor/lib(/.*)?                u:object_r:system_file:s0
/data/asan/vendor/lib64(/.*)?              u:object_r:system_file:s0
/system/bin/asan_extract       u:object_r:asan_extract_exec:s0
Refactor sanitized library on-disk layout - SELinux. This CL changes the policy for ASAN files on-disk to support the changes made by the following CLs - https://android-review.googlesource.com/#/c/359087/ https://android-review.googlesource.com/#/c/359389/ which refactor the on-disk layout of sanitized libraries in the following manner - /data/lib* --> /data/asan/system/lib* /data/vendor/* --> /data/asan/vendor/* There are a couple of advantages to this, including better isolation from other components, and more transparent linker renaming and SELinux policies. (cherry picked from commit 33ebdda80fe109dd07e671a6514880d5680a6c35) Bug: 36574794 Bug: 36674745 Test: m -j40 && SANITIZE_TARGET="address" m -j40 and the device boots. All sanitized libraries are correctly located in /data/asan/*, and have the right SELinux permissions. Change-Id: Ib08e360cecc8d77754a768a9af0f7db35d6921a9 2017-03-30 08:03:33 +02:00			`/data/asan/system/lib(/.*)? u:object_r:system_file:s0`
			`/data/asan/system/lib64(/.*)? u:object_r:system_file:s0`
			`/data/asan/vendor/lib(/.*)? u:object_r:system_file:s0`
			`/data/asan/vendor/lib64(/.*)? u:object_r:system_file:s0`
Sepolicy: Add ASAN-Extract Add selinux policies for init script and shell script to unzip a tar containing ASAN libraries on boot. Bug: 36458146 Test: m && m SANITIZE_TARGET=address Test: manual (build steps for tar missing) Change-Id: I5c3cb233aae93ee9985431090af902b0e3c1b0a7 (cherry picked from commit 0b74305011e70bc58490720709e86aac6eb7700f) Merged-In: I5c3cb233aae93ee9985431090af902b0e3c1b0a7 2017-03-22 03:39:01 +01:00			`/system/bin/asan_extract u:object_r:asan_extract_exec:s0`