am: f81b5cdb

Change-Id: I232e0daa8d0287cf8f616db62abb7a9565ae9dbb

am: 6c3a83d2

Change-Id: Id9a83308c1c2204b22f2cf0281da58215c667a0e

am: c08b9c78

Change-Id: I75eccfc310d4d27ddac9c93aab6f594b04fdabe8

am: e5912986

Change-Id: Id23483bcb0d4e4f75e77cb906f9bff258d53290a

am: fb812648

Change-Id: If684f85cd433cd9e9fad8c369fe9f0732739d40b

am: 8ad57ef6

Change-Id: Ia8b668f32c10343fc9704be791e35a84127dc4b0

Delete rule for permission_service since we use packages.list instead.

Test: adb shell storaged -u
Bug: 34198239
Change-Id: Ic69d0fe185e627a932bbf8e85fc13163077bbe6b

am: 20868a1b

Change-Id: I83e355565f11aa6a44973f6c3b4c9a421ff66267

am: 94668169

Change-Id: Iedaf0cb27d1bf4b0cf21a8a827b26fa12dcd326e

Test: pass
Change-Id: Ie1a6513f8fa9cb4b007fccefe63ccb78fcd45578

In order to dump hardware services using dumpsys, dumpsys needs to be
able to talk to the hwservicemanager.

Bug: 33382892
Test: dumpsys --hw works from unrooted shell
Change-Id: I31f0982193991428da465507f93d50646cb38726

am: 6ea577a5

Change-Id: Ifd182b1ab935d1acc4197936161f477920a61f1c

am: 7d98edfb

Change-Id: I77e9a25e3f12da33babd5f4bfe8e5a2f12eae0a0

Test:   Device boots
        Can take photos
        Run "adb shell atrace -c -b 16000 -t 5 gfx" without root and check produces
        output
        Run "python systrace.py view gfx freq sched am wm dalvik
        binder_driver" from external/chromium-trace after adb root and
        check populated
Bug: 31856701
Change-Id: Ic319f8a0a3e395efa7ee8ba33a868ac55cb44fe4

am: f2827964

Change-Id: I0bc94f0af23d692d3d632dc46e5bad15c76823f3

- Allow cameraservice to talk to hwbinder, hwservicemanager
- Allow hal_camera to talk to the same interfaces as cameraservice

Test: Compiles, confirmed that cameraservice can call hwservicemanager
Bug: 32991422

(cherry picked from commit 9c43a3ff)
Change-Id: Ied0a3f5f7149e29c468a13887510c78d555dcb2a

am: a98b9804

Change-Id: I9ee6a1b562eff63a2e09c41fa9ea126f92709ca9

Change-Id: I49ec3c6970ef51a220dbb6d9ec3c6b2b0c94612b

In my commit f41d89eb I forgot to
switch rild and gatekeeperd rules from explicitly associating these
domains with the hal_telephony and hal_gatekeeper to using the
hal_impl_domain macro. As a result, the recent commit
a2519226 inadvertently revoked
HwBinder access from rild and gatekeeperd.

This commit fixes the issue by switching rild and gatekeeperd to the
hal_impl_domain macro.

Test: "sepolicy-analyze out/target/product/bullhead/root/sepolicy attribute haldomain"
      now lists rild and gatekeeperd
Test: "sepolicy-analyze out/target/product/bullhead/root/sepolicy attribute hal_telephony"
      still lists rild
Test: "sepolicy-analyze out/target/product/bullhead/root/sepolicy attribute hal_gatekeeper"
      still lists gatekeeperd
Bug: 34180936
Bug: 34470443
Change-Id: I7949556f58c36811205d5ea3ee78ea5708e95b45

am: 9c4aac9c

Change-Id: Ifae9d87e88b67603d7fc4d2ebd00babe5777ddfd

am: 4eddb3e3

Change-Id: Ic3968a0a3fb4d932b9d05afd0d38a16c96f03388

Fix the following denial:

tombstoned: type=1400 audit(0.0:563): avc: denied { append } for path="/data/anr/traces.txt" dev="sda35" ino=679941 scontext=u:r:tombstoned:s0 tcontext=u:object_r:anr_data_file:s0 tclass=file permissive=0

Bug: http://b/34472671
Test: mma
Change-Id: Iab5fbaf50888aa0f195841cb7e718ff393e526dd

Test: No change to SELinux policy
Change-Id: I45d6d6ab0538b9d4768b922cfdc2c972272d0b18

am: f83bc221

Change-Id: Iebdc9236eb679672d6518d811cc80e4336c8ed6b

am: 937be2b4

Change-Id: I39dcb15e40757ff4340f2c1996e09a1c8f0e1c58

am: fb5495e1

Change-Id: I02acb1fbb2cfaec2ce86ef1b485c0f97d1cf26dd

am: 2b2c74f8

Change-Id: I00841b24d684efe788e7794038f98da55d4c75e9

am: cb7a9c1d

Change-Id: Ibf1c84344b132bcc26fa71eeda93065d78f08948

am: d5b6043f

Change-Id: I95dfe4238c5029a54fcabe3345441fddbb246c5e

As of https://android-review.googlesource.com/324092, ephemeral_app is
now an appdomain, so places where both appdomain and ephemeral_app are
granted the same set of rules can be deleted.

Test: policy compiles.
Change-Id: Ideee710ea47af7303e5eb3af1331653afa698415

am: 000a7b44

Change-Id: I2622546e00f914a5f43ef4dfa490f1f65a1df584

am: 47ab9eaf

Change-Id: I4cda4881143e2bcdc49e9e4c8d5ae4775adf0252

This fixes the following issues introduced in commit
d225b697:
* plat_file_contexts was empty because the target was referencing
  system/sepolicy/private/file_contexts via a misspelled variable
  name.
* plat_file_contexts wasn't marked as dirty and thus wasn't rebuilt
  when system/sepolicy/private/file_contexts changed. This is because
  the file_contexts dependency was referenced via a misspelled
  variable name.
* plat_file_contexts wasn't sorted (as opposed to other similar
  targets, such as nonplat_file_contexts and file_contexts.bin). This
  may lead to unnecessary non-determinism.
* nonplat_file_contexts wasn't marked dirty and thus wasn't rebuilt
  when device-specific file_contexts file(s) changed. This is because
  the file_contexts files were referenced via a misspelled variable
  name.

Test: "make plat_file_contexts" produces a non-empty file containing
      mappings from system/sepolicy/private/file_contexts
Test: "make plat_file_contexts" updates output when
      system/sepolicy/private/file_contexts changes
Test: "make plat_file_contexts" produces output which is sorted
      accroding to rules in fc_sort
Test: "make nonplat_file_contexts" updates output when
      device/lge/bullhead/sepolicy/file_contexts changes (tested on
      aosp_bullhead-eng)
Bug: 31363362
Change-Id: I540555651103f02c96cf958bb93618f600e47a75