google-gs201/android_device_google_lynx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bluetooth: Allow QTI HAL service to access its logbuffer

Browse Source 
Bug: 229691092
Test: Pass file permission check
Change-Id: Ic97bf3b23c452d20e5e32f3bafe2f6b2c5d2be3b
This commit is contained in:
Cheney Ni
2022-07-18 17:36:31 +00:00
committed by TreeHugger Robot
parent b51016a53f
commit 49a3cfae3a
2 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
bluetooth/file_contexts
View File

@@ -1,5 +1,10 @@
# Bluetooth
# Bluetooth HAL service
/vendor/bin/hw/android\.hardware\.bluetooth@1\.0-service-qti u:object_r:hal_bluetooth_default_exec:s0
# Bluetooth Vendor nodes
/dev/btpower u:object_r:bt_device:s0
/dev/ttySAC18 u:object_r:hci_attach_dev:s0
# Bluetooth Debuggable HAL nodes
/dev/logbuffer_btpower u:object_r:logbuffer_device:s0
/dev/logbuffer_tty18 u:object_r:logbuffer_device:s0

1
bluetooth/hal_bluetooth_default.te
View File

@@ -3,6 +3,7 @@ allow hal_bluetooth_default bt_device:chr_file rw_file_perms;
add_hwservice(hal_bluetooth_default, hal_bluetooth_coexistence_hwservice)
userdebug_or_eng(`
allow hal_bluetooth_default logbuffer_device:chr_file r_file_perms;
allow hal_bluetooth_default sscoredump_vendor_data_crashinfo_file:dir rw_dir_perms;
allow hal_bluetooth_default sscoredump_vendor_data_crashinfo_file:file { create_file_perms };
set_prop(hal_bluetooth_default, vendor_ssrdump_prop)