am: c1de2f31

Change-Id: I7febe6164813451ad38449642450e4bfee31480c

am: ba23c8fa

Change-Id: I9170ebe99c6fc5357ff3c92cb47476b85545b8d6

The concept of VNDK-stable set is gone because they no longer need to be
stable across several Android releases. Instead, they are just small set
of system libraries (other than Low-Level NDK) that can be used by
same-process HALs. They need to be stable only during an Android release
as other VNDK libraries. However, since they are eligible for double
loading, we still need to distinguish those libs from other VNDK
libraries. So we give them a name vndk-sp, which means VNDK designed for
same-process HALs.

Bug: 37139956
Test: booting successful with vndk-sp libs in /vendor/lib(64)?/vndk-sp
Change-Id: I892c4514deb3c6c8006e3659bed1ad3363420732

am: 78e8d073

Change-Id: Ia9314f41641d07f3216e82e0bd01b69a10f52d67

am: d0e9cb05

Change-Id: Iac4a9cc2ac78ba9b72a4bb72ff81f9fd98b34d4b

Add read rights for du.

Bug: 30832951
Test: m
Change-Id: I1186ff995684844e9c6092b5ae65c19172fefbbe

am: b9469075

Change-Id: I5da7d1b8ec4a16ee6bf38ed4bb12931dc25071f4

am: 86123070

Change-Id: I92cf85d8c6cd05bd76ab9745546ac8051535d2ca

am: 2f12ebf4

Change-Id: I18d8402f01f2d3c403a2993f9118c25afb014d57

am: 72126e1b

Change-Id: I58972c23929e81f27d28eff0dd66f21240311b7e

The sepolicy version takes SDK_INT.<minor> format. Make sure our
'current' policy version reflects the format and make it '100000.0'.
This ensures any vendor.img compiled with this will never work with
a production framework image either.

Make version_policy replace the '.' in version by '_' so secilc is
happy too.

This unblocks libvintf from giving out a runtme API to check vendor's
sepolicy version. The PLAT_PUBLIC_SEPOLICY_CURRENT_VERSION will
eventually be picked up from the build system.

Bug: 35217573
Test: Build and boot sailfish.
      Boot sailfish with sepolicy compilation on device.
Signed-off-by: Sandeep Patil <sspatil@google.com>

Change-Id: Ic8b6687c4e71227bf9090018999149cd9e11d63b

am: b3ebaef4

Change-Id: Idacaa3e366a4d754d9e645ee6cadca5504df0b1b

am: df720941

Change-Id: I4590b07ef09247aaf632a09f3247c2314d2a1a63

CTS includes general_sepolicy.conf built from this project. CTS then
tests this file's neverallow rules against the policy of the device
under test. Prior to this commit, neverallow rules which must be
enforced only for Treble devices we not included into
general_sepolicy.conf. As a result, these rules were not enforced for
Treble devices.

This commit fixes the issue as follows. Because CTS includes only one
policy, the policy now contains also the rules which are only for
Treble devices. To enable CTS to distinguish rules needed for all
devices from rules needed only on Treble devices, the latter rules are
contained in sections delimited with BEGIN_TREBLE_ONLY and
END_TREBLE_ONLY comments.

This commit also removes the unnecessary sepolicy.general target. This
target is not used anywhere and is causing trouble because it is
verifying neverallows of the policy meant to be used by CTS. This
policy can no longer be verified with checkpolicy without
conditionally including or excluding Treble-only neverallows.

Test: mmm system/sepolicy
Test: Device boots -- no new denials
Bug: 37082262
Change-Id: I15172a7efd9374543ba521e17aead1bdda7451bf

am: c28a5c5d

Change-Id: Idd1d93beb393a9cd31bc2cf35b722920f9e31855

am: b9bd6708

Change-Id: Ie76de5da8e9a370e2f744d158ead93bbc1d0a508

am: 9c7a0d8c

Change-Id: I139d43838b74a8e7340d145d7c644efa090457db

am: 82696dd1

Change-Id: Ib04932a421523eb50c2e40bf24000ae58ac7a535

am: 8ee64187

Change-Id: I6c035c3e696531297ff8a3c09045acf6d2c98cd0

am: 462cf398

Change-Id: I12d310b90e6863a56c1fc269ce237e93864d88f8

am: 36e725e5

Change-Id: I920f2163d0ce225389c9c649061957d23006868c

am: ee97662f

Change-Id: I6e2eba3f0081494508b015f6bd785085638f1cee

darwin's getopt() doesn't like putting arguments
in the wrong order.

Test: Mac/Linux builds
Change-Id: If632e9077c1b5714f91c5adaa04afb4963d9b0f5

am: c7b645c8

Change-Id: I118f8f0390177ae8fdc8115fe502a10b1f3d6426

am: f497d0b7

Change-Id: I8b75d668cbc30b81731aed7421327a3f2f4b19a8

We should give appdomain the access to the /vendor/framework directory
since the jar in the directory is not dexopt-ed.AFAIK, jars which are
not in the bootclasspath are not dexopt-ed by default.

Bug: b/37129319
Test: built and confirmed that embms.apk not crashed

Change-Id: Ic2b1eef472f2fba53e26403dde8ad9ede8105a03

* changes:
  Allow 'su' domain access to vndbinder.
  Modify checkfc to check (vnd|hw)service_manager_type.

am: 8fc97616

Change-Id: I101d321fd855acf15c0cd4617da7b6961cab2a20

am: 77154b39

Change-Id: Ia6c653fcab261084d6dcbb3d3ec8e3311fdf4fca

am: 84b3879a

Change-Id: I64c0a4e8ae9978fe8b809e21ae8b3e9b0b3feb98

am: 04ef57bf

Change-Id: I906f85514efb4301ac0bafaf140deba7be76cdee

Vndk-stable libs are system libs that are used by same process HALs.
Since same process HALs can be loaded to any process, so are vndk-stable
libs.

Bug: 37138502
Test: none, because the directory is currently empty and thus this is
no-op. sailfish builds and boots.

Change-Id: I67a2c8c2e4c3517aa30b4a97dc80dc2800e47b5a

For example, for listing vndbinder services
using 'adb shell service -v list'

Test: adb shell service -v list
Bug: 36987120
Change-Id: Ibf3050710720ae4c920bc4807c9a90ba43717f3b

added checkfc options 'l' and 'v' to verify hwservice_manager_type
and vndservice_manager_type on service context files, respectively.

The checkfc call to verify the new hwservice_contexts files will
be added together with hwservicemanager ACL CLs later.

Bug: 34454312
Bug: 36052864
Test: device boots, works
Change-Id: Ie3b56da30be47c95a6b05d1bc5e5805acb809783

am: 870160d5

Change-Id: Ia54190a372be0ffb8ed573dab31cdce4c0ddbf7a