5e37271df8
system_file_type is a new attribute used to identify files which exist on the /system partition. It's useful for allow rules in init, which are based off of a blacklist of writable files. Additionally, it's useful for constructing neverallow rules to prevent regressions. Additionally, add commented out tests which enforce that all files on the /system partition have the system_file_type attribute. These tests will be uncommented in a future change after all the device-specific policies are cleaned up. Test: Device boots and no obvious problems. Change-Id: Id9bae6625f042594c8eba74ca712abb09702c1e5
21 lines
796 B
Text
21 lines
796 B
Text
# bufferhubd
|
|
type bufferhubd, domain, mlstrustedsubject;
|
|
type bufferhubd_exec, system_file_type, exec_type, file_type;
|
|
|
|
hal_client_domain(bufferhubd, hal_graphics_allocator)
|
|
|
|
# TODO(b/112338294): remove these after migrate to Binder
|
|
pdx_server(bufferhubd, bufferhub_client)
|
|
pdx_client(bufferhubd, performance_client)
|
|
|
|
# Access the GPU.
|
|
allow bufferhubd gpu_device:chr_file rw_file_perms;
|
|
|
|
# Access /dev/ion
|
|
allow bufferhubd ion_device:chr_file r_file_perms;
|
|
|
|
# Receive sync fence FDs from hal_omx_server. Note that hal_omx_server never directly
|
|
# connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
|
|
# those two: it talks to hal_omx_server via Binder and talks to bufferhubd via PDX.
|
|
# Thus, there is no need to use pdx_client macro.
|
|
allow bufferhubd hal_omx_server:fd use;
|